question

42010100 avatar image
0 Votes"
42010100 asked 42010100 commented

A Docker CIM provider in a current SCOM Linux agent . Is it possible ?

Hi again.

In my previous thread I have opened a thread about Docker support in a current SCOM Linux agent.
But on my personal view it deserves to be opened in an another one so I do it .

Well. I have figured out that CIM providers bundles are included into a current agent bundle and they are in a root of installation folder . Current SCOM Linux agent consists of 2 ones for MySQL and Apache. There is no Docker CIMP at all.

Also I found that OMS Linux agent has the one in the similar bundle. I extracted a current docker-cimprov rpm from there and applied it to some of my servers (I have a 1.0.0.32 version on them and new bundle has 1.0.0.37). All of them works fine .

So now I have a way to apply changes. Three ways to be clear-

The first way is to apply rpm or deb (OS depended) for docker-cimprov strictly after an agent install . It is not convenient to me because we had a tons of different linux servers with dozens admins so this procedure would be horrible if I did it on that way.
The second way is to add the docker-cimprov bundle into the current Linux agent 1.6.6.0 bundle . Is it possible ? Is there some articles or white papers about ?
The third way consists of my thoughts about applying OMS Linux agent instead of SCOM Linux agent . Is that possible to replace current SCOM bundles to OMS ones ? Will it work ? Is there somebody who has a similar experience ?

Thanks in advance will wait for your answers

Sincerely
Andrii

msc-operations-manager
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

CyrAz avatar image
1 Vote"
CyrAz answered 42010100 commented

You can use OMS Linux Agent instead of SCOM agent.
Adding the --enable-opsmgr parameter when you run omsagent-blabla.sh --install should do the trick.

· 6
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thanks for the answer, but I see some drawbacks here. When you have mentioned

when you run omsagent-blabla.sh --install should do the trick.

It intends that I should install the agent manually, not by an standard push procedure. It is not a way I like to work to.

IIs it possible to put an OMS agent bundle instead of standard one into an installation folder and use it ?



0 Votes 0 ·

Oh ok.
Then what you could do is first push the regular SCOM agent and then go to the Unix computer views and run the "Configure Linux Log Monitoring" task.
It's not very intuitive from its name, but what it effectively does is that it copies omsagent-1.8.1-256.universal.x64.sh to the Linux server and then runs it with --upgrade --enable-opsmgr parameters (as seen here : https://systemcenter.wiki/?GetElement=Microsoft.Linux.Log.Monitoring.UpgradeAgent.WriteAction&Type=WriteActionModuleType&ManagementPack=Microsoft.Linux.Log.Monitoring&Version=10.19.1006.0 )
It's not the latest version of the OMS Agent, but it still contains the docker provider. You could also try to mimic that task in a custom MP of your own to use the latest version.
Also that will likely require some updates to the sudoer file, as the the .sh file name is different and probably tries to do more stuff than the regular SCOM agent.

1 Vote 1 ·

Also I don't know if you could directly push the oms agent using the regular process, I had a quick look at the different tasks involved in the agent push process and it feels like it would involve quite a few unsupported hacks to make it work (if it is possible at all).

1 Vote 1 ·

Sounds silly ..but I see no such task in my list.Well I will try to find a decision/

0 Votes 0 ·
Show more comments
CyrAz avatar image
0 Votes"
CyrAz answered 42010100 commented

That's not the one, I'm talking about Linux Log File Monitoring , aka Microsoft.Linux.Log.Monitoring ( https://systemcenter.wiki/?Get-ManagementPack=Microsoft.Linux.Log.Monitoring&Version=10.19.1008.0 ) and not the Library one.




· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Wow.

Surprise,surprise ! I will dig into it and give you an information about further.

As it takes to my current situation I have made an experiment ,remove agent completely from one of my Linux servers (from SCOM console ) then install it . After agent has completely installed I added to this server (CentOS 7) docker-cimprov rpm from earlier agent version (1.0.0.32) with a standart way - rpm -i docker-cimprov. Then I invoked scxadmin --restart . After 2 hours I had a full info about all my docker instances and containers on the server. So this might be a way, temporary though 8(

Nevertheless I keep on explorating how to deal with it. I will add MP you've mentioned and do some other things to resolve it.

Cheers.

0 Votes 0 ·

Just an idea, but you could also create a task that would push and install the docker provider only; it should work in the same fashion as the native Configure Linux Log Monitoring task (which pushes the full OMS)

1 Vote 1 ·

A nice idea ! It should works though .

0 Votes 0 ·