I met with an interesting issue. We have SCOM 2019 UR2 recently upgraded from 1807.
All works fine.
Include Docker Monitoring MP by V.Zelenov.
I see all docker daemons and containers on agents presented in SCOM .
But when I try to add a new server I literally run into the wall.
Here is a short description what I do -
1. Most Linux servers here are made from a "first and only clone" where the last 1807-like Linux agent has already been installed.
2. So in a first hand I log in into that server, make a certificate with an scxsssl there and run a discovery to find it. The server is found in 2-3 sec, the discovery usually performs only certificate signing and I have a new Linux server monitored by SCOM. 3. Then I wait approximately 20-30 minutes to end all processes up .
When I see that the server is completely discovered I upgrade it to the most recent version (1.6.60 AFAIK). All processes are fine so that I have an upgraded agent . But there is an issue - docker daemon is not detected by discovery from MP . At all. The discovery is enabled for all of linux servers . MP works fine for all servers except this one . I have dug through all the logs on SCOM servers in Linux monitoring pool. No luck.
I am aware about On-Demand Discovery Task , but it works only for Windows Agents, not for Linux ones.
Is there a way to find what is wrong with my server or run the discovery on demand like it does for Windows ?
Any answers would be appreciated