Agents no longer being discovered

Hey All,

Not too long ago we updated our system to 2020.2.6 and ever since we have not been able to "discover" the agents we have in our environment. When I create a new discovery, it only shows "96 nodes currently polled by an agents" but we have over 400 servers with agents installed.

In the past we've used the "Check existing nodes polled by an agent for node changes and updates" option to ensure that any volume size updates are taken care of during discovery but since this is what's not working.

A little bit more info...we deploy the agent as part of the server build and let the discovery job suck in the resources we want monitored (fixed disks, CPU, memory etc). For some reason the discovery jobs don't detect these agent. Could there be a cache in the DB that isn't being cleared? We do have a ticket open with SW support but they're less than responsive when it comes to "interesting" issues like this and we're tired of running the config wizard and provide fresh diags every week only to receive a response that they can't find anything. Maybe one of you all has seen this before?

Thanks in advance for any advice/suggestions!

Find more posts tagged with

sam

Agent

agent issues

discovery

Accepted answers

All comments

christopher.t.jones123

@luis.wiedemann, agent discovery is polling engine specific, meaning that the discovery is only going to discover agents that are assigned to the polling engine that the discovery is kicking off from. Do you have multiple polling engines?

luis.wiedemann

That's a very good bit of information that I was missing! We have two polling engines that agents are assigned too and while a few more servers have made their way in, I'm still not seeing fixed disks being monitored for a number of agents. I have a call scheduled with support for tomorrow but again, this is the third call with support (and countless diags run) so I'm not terribly hopeful they'll find the root cause here. Maybe I should be more optimistic!

Are there any logs I can review that would maybe point us in the right direction? I've looked through the discovery logs a bit but there's not much I can see for the specific nodes that are affected by this.

Thanks again for the reply!

christopher.t.jones123

@luis.wiedemann, can you provide a little more information? When you say that you don't see fixed disks being monitored, is this after you have selected the resource, don't see the resource available to monitor, the discovery is not set to auto-import with fixed disk checked and they are not being selected?