-
Hello,
I am currently testing IcingaDB in a local test environment. In the _Check Statistics_ section is a nice visualization of _Last Update_ and _Next Check_, both are indicated by blue dots. The…
mcktr updated
4 years ago
-
If a new checkable has been created, we do 2 things:
- Insert state (Pending) into redis -> Synced by initial config sync
- Schedule first check and insert result into redis -> Synced by continuou…
N-o-X updated
4 years ago
-
`last_update` is used to display when a host/service has been last checked. Since IcingaDB this column is updated on every row update which will then be out of sync with the real time when the last c…
-
If there are any custom vars assigned to a user (like shown below, the favourite animal) are not displayed in the front end.
Host and Service custom vars are displayed in their detail views.
I feel …
-
Hi,
While this request might sound weird in the first place it could be helpful with huge setups, especially when thinking about IcingaDB. Maybe it's total BS but at least it should be considered a…
-
-
# Describe the bug
when try to create a new handler , but selected by hostgroup, it fails with "no host filter"
-
This issue has been migrated from Redmine: https://dev.icinga.com/issues/10916
**Created by gilbertaispuro on 2015-12-28 17:58:23 +00:00**
Assignee: _(none)_
Status: _Closed_ (closed on _2016-02-18…
-
Example:
- check_interval = 1m
- Reschedule check to now + 1h
=> Checkable is overdue 1 minute later => 59 minutes before next check should happen
N-o-X updated
4 years ago
-
Hello,
Starting about a year ago we started having issues when a servers that we monitor goes down uncleanly and reboots (i.e. during an out of memory event). Normally, after the reboot, Icinga rec…