An on-demand discovery for Linux - is that possible ?

Андрій Верещака 181 Reputation points
2021-03-29T19:14:40.46+00:00

Hi !
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
Thanks

Andrii

Operations Manager
Operations Manager
A family of System Center products that provide infrastructure monitoring, help ensure the predictable performance and availability of vital applications, and offer comprehensive monitoring for datacenters and cloud, both private and public.
1,413 questions
0 comments
Accepted answer
  1. CyrAz 5,181 Reputation points
    2021-03-30T08:17:39.55+00:00

    The Docker MP relies on a Docker provider that is only included in the OMS agent for Linux (fully compatible with SCOM) and not in the SCOM agent itself, even the latest ones if I'm not mistaken.
    That probably explains why the discovery is not working...
    It may be possible to install this docker provider alongside the SCOM agent, since the providers are kind of "modules" for the scx agent; but I'm not too sure how.

    0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Андрій Верещака 181 Reputation points
    2021-03-30T18:32:17.463+00:00

    Cyril thanks for your thoughts !

    How could I check what kind of providers I have on currently installed agent ? Is there some articles or docs about it ?
    well I have found it

    https://social.technet.microsoft.com/Forums/en-US/76b942e2-9c67-4332-93fb-3a262bcebbae/scx-agent-providers-management?forum=operationsmanagerunixandlinux

    Mr. Chalakov, I send you my deep thanks !

    0 comments
  2. Андрій Верещака 181 Reputation points
    2021-04-01T11:45:35.773+00:00

    Hi !

    This is my final post here so I am going to get answer to me 8)

    Firstly, yes, cim-providers are existed in an install bundle . A current bandle 1.6.6.0 has only 2 providers , for mySQL and Apache, no Docker at all.
    Secondly I am creating an another thread here to figure if it possible to support Docker in standard agent either

    Thank you !

    0 comments