Following issue:
Icinga 2.9.5
Graphite 1.1.0 (running in a pod)
Basically all running fine, icinga and graphite (even though running in OEL8), all good, BUT:
Iāve created a Dashboard, showing only graphite graphs (donāt wanna see the check-result but only graphs of certain services/hosts (like cpu, vmstat, and so on). I did this by setting up the desired view from main menu āGraphiteā ā āServicesā ā filtering the whole bunch
This results in a URL which Iāve copypasted into a new dashlet (basic icinga dashboard).
Works well, all desired graphs are being shown in the dashboard
BUT: this dashlet - in contrary to default like āCurrent incidentsā or āOverdueā - does NOT auto-reload. I have to manually click the refresh-swirl. Fine for me but my plan is to set this up for a department-user (or kiosk), where clicking is no option.
My guess: somewhere under the hood the dashboard is being refreshed if dashlet-URL contains āmonitoring/list/blaā but in my case its āgraphite/list/blaā
(full dashlet url: graphite/list/services?service=host_check_cpu&(host=important_server1|host=important_server2)&graphs_limit=2 )
So my quite simple question: can I get my graphite-dashboard being auto-reloaded? I really hope its feasible somehow
Hi, this works fine for me here. Using the same URL resulting in two graphs.
How did you notice that it doesnāt refresh? Note that the interval of the other contents are usually 10 seconds, the graphs are refreshed every 30 seconds though.
well, all other pages do autorefresh, e. g. āCurrent Incidentsā-Dashboard; also, in parallel opened those checks in a seperate tab; all pages do autorefresh, except those graph-dashboards
After a couple of hours one do see the gap
auto-refresh is set, also it works well for all other dashboards and check-pages (basically everything else but this single dashboard-page containing graphs only)
For testing purpose Iāve put a service-check aside, outcome: the service-check frame is being auto-reloaded, but NOT the graph-frame; this one remains un-refreshed
Iām suspecting that the āissueā is rooted somewhere in this avalanche of icinga-php-files, as only monitoring/list-urls are being refreshed but nothing containing graphite/list-urls, but tbh my php-knowledge is too weak
We also werenāt happy about it but it coincided with us wanting to buy support anyways so we begrudgingly changed to the pay walled repo.
From the quite severe blow back, I think migrating away is a bit hasty as I believe a alternative will spring up soon in the form of a community repo or a free tier matching REHL licencing.
Migrating to Debian or Docker are also options - I would run on Debian if not for my external partners being more confident on RHEL based systems.
