Skip to content
This repository has been archived by the owner on Apr 11, 2024. It is now read-only.

check_haproxy_stats.pl: perfdata and graphite/carbon #24

Closed
GerMalaz opened this issue Aug 6, 2019 · 3 comments · May be fixed by #28
Closed

check_haproxy_stats.pl: perfdata and graphite/carbon #24

GerMalaz opened this issue Aug 6, 2019 · 3 comments · May be fixed by #28

Comments

@GerMalaz
Copy link

GerMalaz commented Aug 6, 2019

hi, got this error in /var/log/graphite/console.log:

03/08/2019 23:55:24 :: Error parsing metric icinga2.lb1.services.haproxy_webfarm.haproxy-stats.perfdata.webfarm-www1=0;52428;58982;0;65536;webfarm-www2=0;52428;58982;0;65536;webfarm-www3=0;52428;58982;0;65536;webfarm-www4=0;52428;58982;0;65536;webfarm-BACKEND.max: Cannot parse path icinga2.lb1.services.haproxy_webfarm.haproxy-stats.perfdata.webfarm-www1=0;52428;58982;0;65536;webfarm-www2=0;52428;58982;0;65536;webfarm-www3=0;52428;58982;0;65536;webfarm-www4=0;52428;58982;0;65536;webfarm-BACKEND.max, invalid segment 52428

graphite expects the perfdata to be separated by spaces, like this: (just one proxy here):
Check haproxy CRITICAL - server: webfarm:www3 is MAINT; |webfarm-www1=3;52428;58982;0;65536; webfarm-www2=2;52428;58982;0;65536; webfarm-www3=0;52428;58982;0;65536; webfarm-www4=5;52428;58982;0;65536; webfarm-BACKEND=10;800;900;0;1000;

Thanks,
Gerardo
@iuriaranda
Copy link
Contributor

Hi @GerMalaz ,

We're not actively using that specific script at the moment, so I can't really test it nor reproduce your issue. Would you be willing to submit a PR for it?

Regarding what you mention, my only concern about changing the format to what graphite expects is that it might break other tools or integrations that expect the current format.

@KlavsKlavsen you being one of the last contributors to this script, what do you think about this?

@KlavsKlavsen
Copy link
Contributor

KlavsKlavsen commented Aug 8, 2019 •
edited
Loading

@iuriaranda We don't actually use the performance data part - as we get that directly via out collecter on the servers.. I wouldn't recommend anyone to use the performance data from icinga/nagios checks.. all monitoring that builds on statistics (collected in graphite/prometheus) - is being queried directly from our icinga.. and if that checks replaces a check on the servers - thats just a benefit.

@iuriaranda
Copy link
Contributor

Due to the lack of activity on this issue, I'll go ahead and close it for now. @GerMalaz feel free to re-open it or open a new issue if you want to tackle this further.

trefzer added a commit to cirrax/monitoring-plugins that referenced this issue Jul 9, 2023
@trefzer
fix stat data in check_haproxy_stats
db17faf 
closes: skyscrapers#24
@trefzer trefzer mentioned this issue Jul 9, 2023
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix stat data in check_haproxy_stats cirrax/monitoring-plugins
3 participants
@iuriaranda @KlavsKlavsen @GerMalaz