Integration
N-able N-central in IDA: open incidents next to all the others
N-central watches the customer infrastructure. IDA fetches the open incidents and shows them in the same widget as every other source - one click turns one into a ticket at the right customer, with a deadline and an owner.
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 N-able N-central
- Open incidents per organisational unit
- The organisational structure of the N-central (customers, sites)
- Alert text and severity
What IDA does with it
- One monitoring view for every source: N-central sits next to Checkmk, UniFi and Server-Eye, not in a window of its own
- The alert becomes a ticket - with customer, SLA deadline and owner
- Mute a single alert, a device or an entire customer - with an expiry, so a known building site does not ring every night
Who it is for
Service providers using N-central as their RMM who want to work alerts as traceable, billable tickets.
Setup: Create an API-only user in N-central, store its key in IDA and map the organisational units to customers. That mapping is deliberately manual: identical company names across systems are normal, and a name match would not be proof.
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: N-able N-central. N-able N-central is a trademark of its respective owner; IDA connects to the system technically, which implies no partnership.
Related
- Checkmk - Monitoring
- Server-Eye - Monitoring
- UniFi Network - Monitoring
Questions about the N-able N-central integration
N-central or N-sight?
N-central. N-sight is a different product with a different interface. The REST API from N-central 2023.9 onwards is required.
Does IDA write back into N-central?
No, the integration reads. The published API has no acknowledge endpoint - which is why an alert is muted in IDA rather than offering a button that would fail against the remote system.
What if the N-central is briefly unreachable?
The last known state stays and the display says how old it is. A network hiccup does not empty the list - a suddenly empty incident list would be the most dangerous false report.
Everything in one interface - for you too
30 days free, no payment details. Every integration is included at no extra cost.