Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Scheduled discovery keeps finding the same nodes, and wont clear them after importing

Scheduled discovery keeps finding the same nodes, despite already being imported, and wont clear them after importing.

I have a scheduled discovery job that runs every day, and even though I have imported the nodes from the last time, the discovery job keeps finding the same servers, and lists them as "Changed".

Even though nothing has actually changed on them, I go to import them to try to clear them, and when it gets to the "Results" phase, every single item reports "Import Status: skipped, already exists in Orion DB". I click Finish Anyway.

Then, when I look a the Scheduled Discovery results, the same three servers are still sitting there in that list. the next day, the Discovery job starts over again with the same nodes and the same phenomenon.

How do I clear these out and get Discovery to stop finding things that already exist?

Find more posts tagged with

discovery

Accepted answers

All comments

lynchnigel

Likewise I have a similar/same issue because i'm using an additional poller I think, but shouldnt it be able to know? I get the nodes that are on there in the discovery and dont clear out unless i tell of course I choose to ignore the nodes.

Mine lists them as 'NEW' found.

Import Status: skipped, already monitored with different engine

FormerMember

I ended up calling support, and they had told me that it was probably because of my secondary poller as well. They showed me how to exclude the components, as opposed to the whole node, but I am not at all satisfied with that answer/solution. Just for kicks and grins, I moved the nodes to the primary polling engine, and allowed the discovery to run as usual. It did not clear the issue, which makes me think that the answer is not 100% accurate.

Also, if I am excluding objects, and a change actually *does* occur, I would then run the potential of missing it.

lynchnigel

That's precisely why I haven't excluded them!

I'm not sure as yet (with only having the additional poller a short while) if discovering from the additional poller would make any difference. Physically from the server which sorts of defeats the object of being able to move them between polling engines.

andrews_j

I have the same issue, but mine are related to other apps, like Windows Scheduled Task. I have 184 objects that just won't purge from the scans. I import them, they are all skipped because it already exists, but are never purged from the 'results' of the scan. How can we get these to purge if they were skipped as already existing? I'm not going to ignore them, they aren't something to be ignored, I want them purged after they have been identified as already existing.

randy.clutter

Here is a work around I have discovered. After you are finished importing all the nodes, you can Edit the Scheduled Discovery to get rid of the results left behind. You do not need to change anything in the scheduled discovery, just click through the wizard all the way through the end and it will wipe out the results.

It's not optimal to do that, but better than nothing.