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

No Graphs from graphite for Week, Month, Year ... #59

Open
Loken22 opened this issue Jul 6, 2016 · 5 comments
Open

No Graphs from graphite for Week, Month, Year ... #59

Loken22 opened this issue Jul 6, 2016 · 5 comments

Comments

@Loken22
Copy link

Loken22 commented Jul 6, 2016

Hi,

icinga2 w. icingaweb2 and graphite runs quite perfect in drawing graphs for 10min to 1 day so far, but fails to draw the graph for 1week, 1month and 1year. even grphiteweb-app. dind't show the graphs for named period and no error is displayed in the error log.

Anyone an Idea?

thx,
Lo

@Loken22 Loken22 changed the title No Graphs for Week, Month, Year ... No Graphs grom graphite for Week, Month, Year ... Jul 6, 2016
@Loken22 Loken22 changed the title No Graphs grom graphite for Week, Month, Year ... No Graphs from graphite for Week, Month, Year ... Jul 6, 2016
@sbancal
Copy link
Contributor

sbancal commented Jul 8, 2016

Hi,

I had a kind of the same issue (I guess). It could be fixed by fixing Graphite's storage-schemas.conf file.
What we had was, retentions = 1m:31d,15m:5y.

With such config, Graphite had a storage place for a value every minute, but Icinga was doing a check every 5 minutes only. That means that the .wsp file had only 1 of 5 values filled for that 1st retention.
This is enough to plot the 1st graph.
But when data has to be aggregated from 1m:31d to 15m:5y, the Ratio of valid data points set to, let say 0.5 (50%) is never met; which means aggregation to 2nd retention spec never occurs.

The fix was to adapt the 1m to Icinga's check interval : retentions = 1m:31d,15m:5y to retentions = 5m:31d,15m:5y.
That way, new *.wsp files would correctly be filled.
To migrate existing *.wsp files, we used :

find /opt/graphite/storage/whisper/icinga2/ -type f -name '*.wsp' -exec /opt/graphite/bin/whisper-resize.py --nobackup \{\} 5m:31d 15m:5y \;

(please read and check twice before copy-n-paste on your production).

Hope this helps.
Regards,
Samuel

@helge000
Copy link
Contributor

I also tried to document the necessary settings. See #56. Feedpack appreciated.

@sbancal
Copy link
Contributor

sbancal commented Jul 22, 2016

That's a good point. I don't know if we should write something about how to set it accordingly to the Icinga's settings (and not to have the problem related in this issue).
It could be here in the README.md , or maybe in a "FAQ" somewhere?

@helge000
Copy link
Contributor

You mean setting up graphite in general @sbancal? I think this topic is much too diverse for this project (we need to cover source and package installs for different OS).
There are also several options where to put this; remember we have graphite/carbon also as a feature in icinga2 core. The issue setting the correct storage.conf should be fixed there - but does not manifest really until using this graphite module

But I think a link to Graphite Web could do the trick?

@sbancal
Copy link
Contributor

sbancal commented Jul 22, 2016

@helge000 You're right, I agree.

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