Any report or query we can use to verify if data collected sucessful for all agent (windows/unix)

Question

Sometime even agent status show healthy but data for reporting are not collecting. Manually check the performance rule one by one are time consuming

Any reports or query we can use to list all the agent (windows/unix) that no collecting data or collecting successfully?

Answer 1

I can't think of an easy way to do this.
If it happens frequently, you should rather try to find out why it's happening...

Answer 2

Hi @Chua Liang Wei ,

I can confirm that there is no such report or even something similar. I would say that you need to do some troubleshooting and find out what is going on. Checking perfomance collection rules won't help you in any way if the issue is intermittent.
I would suggest the following:

• Update your SCOM with the latest Update Rollup
• Update all Linux MPs to the latest version
• Update your Linux agents after the MP update
• Look for related events in the event log of every management server, which is part of the Linux monitoring ressource pool.

I would also encourage you to go through the following posts and consider the relevant suggestions:

SCOM 2016 successful linux/unix agent deployment but no performance data(disk space, processor etc)
https://social.technet.microsoft.com/Forums/en-US/d4c21c41-ee68-4a20-b208-6fae13a63cba/scom-2016-successful-linuxunix-agent-deployment-but-no-performance-datadisk-space-processor-etc?forum=operationsmanagerunixandlinux

SCOM Linux agent longer working after upgrade to 2019
https://learn.microsoft.com/en-us/answers/questions/100980/scom-linux-agent-longer-working-after-upgrade-to-2.html

In the second article you will find reference to the following article:

Troubleshooting monitoring of UNIX and Linux computers

Please try to enable the logging as described in "Enable Operations Manager Module Logging" and also "Enable Operations Manager Logging for Windows Remote Management" as they relate to gahthering data and could help you identify the cause.

Hope I was able to help!

----------

(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

Regards
Stoyan

Answer 3

On a second thought, if you have identified a specific counter that tends to fail regularly, I guess you could create a Powershell monitor that would query the OperationsManager DB for that specific performance counter and check when was the last time a new value was inserted in the DB.
If it was longer than 30min-1h, then make the monitor go to error.