Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Insufficient Metrics sent from InfluxDB09 #122

Open
mantoine96 opened this issue Sep 5, 2016 · 2 comments
Open

Insufficient Metrics sent from InfluxDB09 #122

mantoine96 opened this issue Sep 5, 2016 · 2 comments

Comments

@mantoine96
Copy link

Hi !

First of all, big thanks for your work. It does work wonderfully, and allows us to easily link our Check_MK monitoring to our dashboards.

However I've been noticing that the perfdata files are not deleted upon treatment, and by looking at the logs I found this :

September 05 14:33:15 graphios.py CRITICAL keeping /omd/sites/$SITE/var/graphios/spool/host-perfdata.1473078034, insufficent metrics sent from influxdb09.
Should be 200, got 0

After taking a deeper look at the logs, it seems that InfluxDB is unable to parse the check-mk-host-ping results and generates a 'missing tag value' error.

unable to parse 'check-mk-host-ping!-w200.00,80.00%-c500.00,100.00%,host=KVM,check=rtmin value=0.0 1473078027000000000': missing tag value"}

Is this a known error or do you know any possible fix ?

I am using the latest Graphite (git cloned today : 05/09/2016), with influxDB 0.13.

Thanks a lot !

@mrmike1
Copy link

mrmike1 commented Oct 14, 2016

same issue here with influxb1.0

@onlybytes
Copy link

onlybytes commented Jun 7, 2017

Well, you can say that its a bug or not a bug.
As per your data, this full string "check-mk-host-ping!-w200.00,80.00%-c500.00,100.00%" has many commas. That means there are tags and there are no values.

If you want to get around this, you have to manually change the code in graphios_backends.py file.

The HOSTCHECKCOMMAND macro is taken as it is to construct the path. So in your case since HOSTCHECKCOMMAND is "check-mk-host-ping!-w200.00,80.00%-c500.00,100.00%", it is used as path.

Had your check been just "check-mk-host-ping" then it would have worked.

example of the change that would be required is:

paths=m.HOSTCHECKCOMMAND.split("!",1)
path=paths[0]

Well, you can also write it as:
path,arguments=m.HOSTCHECKCOMMAND.split("!",1)
But, this will fail if the split results in only one value.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants