Monitoring & incidents
Monitoring in the service desk - the alert becomes a ticket
Four monitoring systems, one view: IDA fetches the open incidents and shows them together, sorted by customer. One click turns an alert into a ticket with a deadline and an owner - instead of a second browser window somebody has to keep open.
No payment details · Hosted in Germany
What it does
Checkmk, UniFi Network, N-able N-central and Server-Eye in one shared widget - with a single severity scale across all of them
An alert becomes a ticket against the right customer, with an SLA deadline and an owner
Alerts are scoped by customer: whoever looks after certain customers only sees their incidents
A reporting delay per tenant: an incident has to persist for a configurable time before it alerts - brief blips wake nobody
Push notifications for incidents, optionally for warnings too - bundled rather than one per second
An all-clear as soon as the source stops reporting the incident
Mute a single alert, a device or an entire customer - with an expiry, so a known building site does not ring every night
Set a maintenance window where the source supports one, instead of switching to its portal
Collection happens on the server in the background, not in every open browser: the load depends on the number of systems, not the number of screens
The display says how old the state is - and a failed fetch leaves the last known state standing instead of emptying the list
In practice
In practice
A server fails at a customer site during the night. The incident persists for two minutes, then IDA pushes it to whoever is on call - with the customer and the alert text. One click turns it into a ticket with an SLA deadline. The work is booked onto that same ticket and the maintenance window for the restart is set along the way. The next morning it is clear what happened, who reacted and how long it took, without anyone assembling that from three portals.
Frequently asked questions
Does IDA replace my monitoring?
No. Monitoring stays with the system you have for it. IDA turns the alert into a traceable ticket with ownership, a deadline, recorded time and billing.
Can several monitoring systems be connected at once?
Yes. Unlike phone systems, two monitoring tools are not fighting over the same truth: one customer sits on one, the next on another. All alerts flow into the same widget.
What happens if a monitoring system is unreachable?
The last known state stays, and next to it you see how old it is. A suddenly empty incident list would be the most dangerous false report - a network hiccup is not an all-clear.
How do I stop a known building site alerting every night?
By muting it - the single alert, the device or the whole customer, with an expiry if you like. Where the source has its own maintenance window, you can set it straight from IDA.
Does everyone get every alert on their phone?
No. Push is opt-in, and visibility follows the customer assignment: whoever looks after certain customers is only woken for their incidents.
Try IDA free for 30 days
No payment details. One price, everything included.