Integration
Server-Eye in IDA: alerts, notes and maintenance windows in one place
Server-Eye reports when a sensor trips. IDA fetches the open alerts for every customer in one pass, shows them in the shared monitoring widget and turns one into a ticket on click - the maintenance window can be set along the way.
BetaThis integration is built and usable, but has not yet run against a production third-party system - it was written against the vendor’s public interface documentation. Expect some follow-up work on first connection. We would rather say so up front than let you find out.
What IDA reads from Server-Eye
- Customers, containers and sensors of the estate
- Open alerts with their text and timestamp
- Notes on an alert and maintenance windows in force
What IDA does with it
- One bulk fetch across the whole estate instead of a query per customer - which keeps the load small even with many customers
- The alert becomes a ticket with customer, deadline and owner
- Set a maintenance window on the container straight from IDA, instead of switching to the portal
- An alert carrying a note counts as being worked on - whoever is already on it should not be called twice
Who it is for
Service providers monitoring their estate with Server-Eye who do not want to bridge alert and billable work by hand.
Setup: Store an API key; the customers from Server-Eye are then mapped to customers in IDA. A key is enough - it can be withdrawn on its own, without touching a user account.
Every integration in IDA has its own switch. Turn it off and it disappears completely - including the columns, filters and reports that belong to it. You only see what you actually use.
Vendor website: Server-Eye. Server-Eye is a trademark of its respective owner; IDA connects to the system technically, which implies no partnership.
Related
- Checkmk - Monitoring
- N-able N-central - Monitoring
- UniFi Network - Monitoring
Questions about the Server-Eye integration
Why do all alerts have the same severity?
Because Server-Eye does not grade them. Inventing a grading would be a claim about somebody elses data. An RMM only reports once a configured threshold trips - so every open alert counts as critical.
Can a maintenance window be set from IDA?
Yes, for the container and with a duration in hours. The interface cannot be more granular, and it has no scheduling for a window in the future.
Can IDA re-check a sensor?
No. Restarting a sensor is something else than re-running a check; under the same label it would mislead. What the source does not offer, IDA does not offer either.
Everything in one interface - for you too
30 days free, no payment details. Every integration is included at no extra cost.