I'm trying to test the configuration of my Insight Discovery scanner with only 3 endpoints total: 2 servers and 1 laptop. The laptop has the agent installed, while the 2 servers are being connected to by the scanner directly via the scan settings.
When I run the scan manually by executing `discovery.exe` in the terminal, it finds both servers, executes the scans and uploads to the cloud successfully, updating associated CI assets and everything is fine.
When I run the discovery agent scan manually by executing `discovery.exe -stad`, it kicks off the agent scan successfully, and some time later, the cloud eventually updates (5-10 minutes at least). When it does this, it marks both servers as "NOT FOUND". Why is this happening and how do I prevent it?
Hi Blake,
This is happening because by default, every import you do, updates every host you have on Insight, and since your last import had only one host (your laptop), Insight missed the 2 servers and updated them to "Not found".
You need to adjust your import configuration to fix this. Look for object type "Host" in your import configuration (Insight).
Configure this object and look for the field: Missing objects
Change the value from "update" to "Ignore".
After that you shouldn't have the same issue. If you wish, you can delete the two previously updated servers and import them again.
Journeys is a brand new feature in Jira Service Management that helps you streamline various processes in your organization that may cross multiple departments, such as employee onboarding or off-boarding that require action from different teams. ✨
Join the EAP →Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.