You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When adding a dashlet to the existing and preconfigured dashboards "Current Incidents" and "Overdue", the dashlets are added twice. Also, I can't delete any dashlets from those two dashboards. Modifying the dashlets works fine. Modifying one dashlet also modifies the twin.
Adding dashlets to newly configured dashboards adds them only once, and dashlets are easily deleted. I already removed all dashlets that still worked through the obsolete monitoring module and not the IcingaDB.
To Reproduce
Create any sort of query in Icingaweb, e.g. for Host Problems.
Add the query as dashlet to the aforementioned dashboards.
Also, try to delete any sort of dashlet from those dashboards
I can't reproduce the issue with my colleague's dashboards or in the testing environment.
Expected behavior
Adding a dashlet should only add it once, and they should be deletable.
Screenshots
Screenshot of Dashboard Settings:
The doubling is not apparent in the /etc/icingaweb2/dashboards/[username]/dashboard.ini:
[Current Incidents]
title = "Current Incidents"
[Current Incidents.Service Problems]
url = "icingadb/[...]
title = "Service Problems"
[Current Incidents.Host Problems]
url = "icingadb/[...]
title = "Host Problems"
I think you've guessed it already: I cannot reproduce this. I get no duplicates and removal as well as editing works fine.
I can't reproduce the issue with my colleague's dashboards or in the testing environment.
The doubling is not apparent in the /etc/icingaweb2/dashboards/[username]/dashboard.ini:
If you can reliably reproduce this on your system, try a different browser, log in as a different user, change the locale. Or identify any differences between you and your colleagues. (Maybe they don't have access to a particular module)
However, the dashboard.ini generally doesn't seem to contain all configuration items for the dashlets in the default dashboards.
That's normal. Only once a default item is adjusted, it appears in the INI file.
Describe the bug
When adding a dashlet to the existing and preconfigured dashboards "Current Incidents" and "Overdue", the dashlets are added twice. Also, I can't delete any dashlets from those two dashboards. Modifying the dashlets works fine. Modifying one dashlet also modifies the twin.
Adding dashlets to newly configured dashboards adds them only once, and dashlets are easily deleted. I already removed all dashlets that still worked through the obsolete monitoring module and not the IcingaDB.
To Reproduce
I can't reproduce the issue with my colleague's dashboards or in the testing environment.
Expected behavior
Adding a dashlet should only add it once, and they should be deletable.
Screenshots
Screenshot of Dashboard Settings:
The doubling is not apparent in the /etc/icingaweb2/dashboards/[username]/dashboard.ini:
[Current Incidents]
title = "Current Incidents"
[Current Incidents.Service Problems]
url = "icingadb/[...]
title = "Service Problems"
[Current Incidents.Host Problems]
url = "icingadb/[...]
title = "Host Problems"
[Current Incidents.Recently recovered Hosts]
url = "icingadb/[...]
title = "Recently recovered Hosts"
[Current Incidents.Recently recovered Services]
url = "icingadb/[...]
title = "Recently recovered Services"
[Current Incidents.Late Host Check Results]
url = "icingadb/[...]
title = "Late Host Check Results"
[Current Incidents.Test]
url = "icingadb/[...]
title = "Test"
However, the dashboard.ini generally doesn't seem to contain all configuration items for the dashlets in the default dashboards.
Overdue dashboard:
In dashboard.ini:
[Overdue]
title = "Overdue"
[Overdue.Late Host Check Results]
url = "icingadb/[...]
title = "Late Host Check Results"
[Overdue.Late Service Check Results]
url = "icingadb/[...]
title = "Late Service Check Results"
Your Environment
Include as many relevant details about the environment you experienced the problem in
icinga2 --version
): r2.14.2-1php --version
): PHP 8.0.30Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: