Perf-O-Meter for local checks

General
1

I’m trying to find up-to-date document that covers perf-o-meters and their configuration with regards to localchecks. I’m currently running “raw 1.6.0p11”.

I’ve created a simple local check that returns back the following metrics on a single item:

  • “connections” (number of connections to queue)
  • “depth” (number of messages in queue)
    eg
    0 QueueStatus_TestQueue connections=1|depth=231 Actively processing queue
    I notice the “perf-o-meter” automatically tries to reflect the “connections”, but not the depth (ie, it shows “1” in the image, but not “231”). I would like to be able to show the depth primarily.

The best I can find in the documentation that addresses custom perf-o-meters is a legacy one (https://checkmk.com/cms_legacy_devel_perfometer.html). It appears this method is no longer supported, but I tried it anyway and got an error saying perfometer_td didn’t exist. This is apparently removed in 1.5+.

Could someone point me in the direction of the more recent documentation as I am having a hard time finding it. Else, could someone provide me with a more uptodate example?

2

The problem is that the actual performance data systems looks if there is a definition for your metrics and for your check command.
If nothing is found for the check command it tries to find some information for the single metrics. “connections” is a metric name i think where a perf-o-meter definition will exist.
The system is using this without further notice or search.

I know what you want to achieve but i don’t know how to do it in an easy and quick way.

3

Thank you for the response, I think I follow.
So the fact it is trying to show something automatically is probably a naming coincidence. If I changed the name of that metric it’s likely dissapear completely?

It seems likely that unless I can find a way to add new definitions, I would have to rename the metric to avoid it displaying connections as it is, but wouldn’t be able to show a simple graphic for the depth.

4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.