Is it possible to disable the processing of specific perfdata?

Icinga 2
,
1

Hi,

I have a check that is production various perfdatas (check_redis -A from monitoring-plugins-contrib). I am using GraphiteWriter to send the perfdata values to graphite. Most of the perfdata are no problem, but the check produces some text values like f.e. config_file=/etc/redis/redis.conf or atomicvar_api=atomic-builtin, too. The GraphiteWriter emits for each of these perfdata 4 log lines each time a check result is processed:

[2024-12-15 17:52:03 +0100] warning/GraphiteWriter: Ignoring invalid perfdata for checkable 'hostname!REDIS' and command 'passive' with value: atomicvar_api=atomic-builtin
Context:
        (0) Processing check result for 'hostname!REDIS'

Is it possible to specify some perfdata names for a service that should simply be ignored by the GraphiteWriter? It would be great it the values could be stored by icinga2 but not processed by the GraphiteWriter. Or is the only possibility to quiet the log messages by modifying the check?

Thanks,
Alex

2

IMHO it’s only possible to disable all perfdata for a service with enable_perfdata = false. If I had to solve the problem, I would put a wrapper around the check and use a regex in there to filter the output.

2 Likes
3

Hi.

I asked a similar question some time ago.
Maybe this thread helps.
You can drop specific metrics in the carbon-cache.

Greetings,
HomerJay

1 Like
4

Thanks for the advice, but that will not remove the warnings of the GraphiteWriter in the log.

5

I don’t think it’s possible to drop specific perfdata before it gets handed over to the perfdata-writer feature.
However, I think the best way to “fix” this long-term would be to have only valid entries anyways - maybe this is fixable in the check-plugin