-
Notifications
You must be signed in to change notification settings - Fork 91
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
Icinga2 not get all the graphs from grafana , got only ping4 graph #197
Comments
Hi, Kindly provide the solution issue, icinga2 not getting all the graphs from grafana |
Please post your config.ini & graphs.ini. Also what backend you use, which module version, grafana version ..... |
I have similar issue. My "Icinga Web 2" is only showing "Host Alive" performance graph for all my added hosts and services. "Host Alive" is the "Default panel id *: 1" in my Grafana (v5.4.3). I'm using "Icinga2 with InfluxDB" dashboard that I've imported from: https://grafana.com/dashboards/381
My /etc/icingaweb2/modules/grafana/graph.ini is empty and below are the contents of my /etc/icingaweb2/modules/grafana/config.ini:
|
That dashboard is not made to use with the module. please use the provided default dashboard. |
The reason I imported the "Icinga2 with InfluxDB" dashboard was because I'm not able to follow the steps of "Import dashboards" within your Guide The Grafana v5.4.3 that I'm using showed a different interface for importing dashboard. Refer to the screenshot I hope you can assist me as I'm new to Icinga2 + InfluxDB + Grafana. |
I have to take some new screenshots, but technicaly the steps are the same, Import dashboard, point to the file or paste json, select data source. |
Had that same issue, it was all about setting up the right pannel and the right variables to make it show correctly. I agree that the default dashboard will get it working in most cases, without other interaction, but if you don't want the default dashboard, you should get the same results setting up the correct variables, pannelId, and org in the module configuration. (if you can't see it from the web interface, check config.ini). For me the best way to diagnose it is to look at the url that the render is getting it's data from, so you can see for yourself where's the problem. What I didn't get right away was the check_command part. Perhaps that part would need a little help from the code. I mean, InfluxWriter uses |
Forget everything about the |
Expected Behavior
Current Behavior
Possible Solution
Steps to Reproduce (for bugs)
Context
Your Environment
icinga2 --version
):icinga2 feature list
):icinga2 daemon -C
):The text was updated successfully, but these errors were encountered: