Nutanix Monitoring

Checkmk Exchange
,
1

I made an up to date version of my extended Nutanix monitoring.
It brings Nutanix on the “same” level as the ESX monitoring, i hope so :slight_smile:

This version should be the last stand alone extension to this included agent and checks.
I migrated all legacy plugins to the new API and asked for how-to submit the whole bunch of data to the CMK github. A PR with around 50-60 files is not liked by the Munich team i think.

The 2.1 package should also work with 2.0 - if someone can test it, it would be helpful.
The packages marked with 2.2 and complete please ignore.

9 Likes
2

Update - i got information that the 2.1 package is not completely compatible with 2.0
I will have a look at this problem the next days.
The problem are with the check parameters as far as i know.

2 Likes
3

Updated the 2.0 package here

Install is working without problem, quick function test was also without problem.

1 Like
4

Thanks Andreas for these great checks. They’re much more helpful than that what comes with checkmk itself. I hope tribe29 will include this in future checkmk releases.

5

@andreas-doehler I get:
$ cmk -D foo.bar.com
Failed to auto-migrate legacy plugin to check plugin: prism_alerts
Please refer to Werk 10601 for more information.
Failed to auto-migrate legacy plugin to check plugin: prism_containers
Please refer to Werk 10601 for more information.
Failed to auto-migrate legacy plugin to check plugin: prism_info
Please refer to Werk 10601 for more information.
Failed to auto-migrate legacy plugin to check plugin: prism_storage_pools
Please refer to Werk 10601 for more information.

Do we need to remove the existing cmk nutanix integration before?

6

Normally this message is only informational.
What happens on your host if you do a “cmk -vvI foo.bar.com” or a “cmk -vvn foo.bar.com”?

You need to manually remove the old plugins only if you want to use the “–debug” switch.

7

I get

  Source: SourceType.HOST/FetcherType.PROGRAM
  -> Not adding sections: Agent exited with code 1: Caught unhandled HTTPError(HTTP Error 404: Not Found) in /omd/sites/xxx/lib/python3/cmk/special_agents/utils/agent_common.py:135
  Source: SourceType.HOST/FetcherType.PIGGYBACK
8

You can execute the agent manually. The command is shown with an “cmk -D hostname”.
It looks more like, that there is not the right URL requested.

9

Program: /omd/sites/xxx/share/check_mk/agents/special/agent_prism '--server' 'x.x.x.x' '--port' '9440' '--username' 'foo' '--password' 'bar'
Servername, Port, User and Password is ok, but I’m wondering why it seems to use the builtin agent_prism?

10

Ok that is strange - what package of the prism agent from my github do you have installed?
If it is CMK 2.1 than it can be ok
The shown path is only a wrapper and it calls then the right function from ~/local/lib/check_mk/…

11

nutanix_prism-3.0-2.1.mkp We’re running 2.1.0p14

12

What happens if you execute the special agent command manually - some more output or only the same HTTP 404?

13

Found one error inside the special agent and will fix it.

14

Updated package nutanix_prism-3.1-2.1.mkp is available on github.
I hope this was the last copy & paste error.

15

Now also the PR on Github is made to integrate all these fancy new checks inside the base system.
We can only cross the fingers and pray :smiley:

1 Like
16

Hi Andreas
i installed your package for 2.0 (v 3.3) on a 2.0.0p27 and have it run against a Nutanix prism 5.20.3. (i know its not the most recent one but the only one i can test it now).
Where the builtin checks work (1st screenshot), the checks of your MKP throw an exception (2nd screenshot):
grafik
grafik

This is what the crash report looks like of one of the container checks:

grafik
grafik1295×541 18.5 KB

And this is the one of the discovery:

grafik
grafik1360×367 9.11 KB

Let me know if you need more information on this (via DM then?)

BR
Thomas

17

I got the same crash some days before.
It was a problem with the API versions of Nutanix - some calls need API v1 and most other calls v2.

New version online - 3.4
I hope this was the last problem between API v1 and v2 - but API version 3 is waiting :smiley:

18

Andreas, superb work, as always:

grafik
grafik1946×903 94.3 KB

Now i have one crash left:

grafik
grafik1351×659 22.2 KB

I suspect its caused by the hostname (which is its IP)?

BR
Thomas

19

For this i think i need the agent output.
It looks a little bit strange. As it means this host has no memory.

20

Sent a DM to you :slight_smile:

BR
Thomas