tectumopticum
tectumopticum
We can reproduce this issue in 1.9.1. It occurs when we mark services with same servicename on different hosts. If you mark services with different names it works fine.
still reproducible in Icingaweb 2.11.2 + Director 1.10.2
> Same happens in sync rules, when you press "Check for changes", then "Trigger Sync" I cannot confirm this. Otherwise we would have an severe issue with critical impact for...
It would be helpful to plan this maximum value as a configuration parameter instead of a hard-coded value in the code: sometimes users set a downtime to a max-value over...
> ref/NC/819325 see #463
I'm also missing this information in the alarms of the vmhosts. A message like "\_ [CRITICAL] Overall VMware status is 'red'" is probably not sufficient or helpful for informing an...
I'm not sure if my problem has the same root-cause. We're on "icingadb-only", which means the monitoring-module is disabled and the IDO-DB has been dropped. Since then klicking on the...
> Hello @tectumopticum > > My configuration is also completely icingadb/icingadb-web (ido completely disabled). > > On my production (6k objects, 230k services) everything works perfectly. After 6 minutes I...
The same applies for "update-icinga -name agent": all individual settings of the agent-service like "Recovery" or "Startup type" were reset after updating the agent.