I don’t know either
I made this a couple years ago, it worked great back in time, but unfortunently i didn’t kept it up2date to newer checkmk versions.
Obviously everyone is free to share their inputs and open some issues on git for me to try to help and improve any bug community founds out.
Still, i’m glad that somehow you got it working with a few changes only.
Maybe you could make a pull request on git with your changes and by that helping out others.
Oh no. This agent is still on Python 2, whereas current Checkmk uses Python 3.
Do not symlink /usr/bin/python3 to /usr/bin/python.
Use #!/usr/bin/env python3 as shebang line in the special agent script and use 2to3 to convert it to Python 3.
Your screenshot shows that this extension package was made on Checkmk 1.5.0p25 in March 2021. This was an old version even back then. I would not expect this extension package to work on Checkmk 2.0 or 2.1 as we have gone through the Python 2 to 3 transition.
I don’t think this is an issue with the Checkmk backend. You can investigate the raw data that the plugin produces using the command OMD[psgmon]:~$ cmk -nvp <host> and look for the service in question (-n: do not submit this to the core, -v: verbose, shows individual service outputs, -p include the metrics in the output).
hello at all, thanks to @Tobias13! after some trouble with xml2dict like described above, works for me too.
but now, only the special agent give outputs. so why did the installed linux agent doesnt queried anymore?
Oh, I thought the numbers where wrong, but the values actually are in the order of hundred thousands to millions. It which sense are they not “displayed properly”? What did you expect? (no sarcasm, it’s a genuine question!)