Alerts

Monitoring belongs in the same place you already work, not in five vendor consoles. Opentra ingests alerts from your tools and can turn the ones that matter into tickets.

Where alerts come from

The alert pipeline ingests from your monitoring and security stack — Level.io (RMM), and endpoint-security and backup providers such as Huntress and MSPBackups. Each alert lands against the client organisation it belongs to, carrying its provider, the device it relates to, and the raw payload for reference.

Severities

Every alert has a severity, and the queue sorts and colours by it:

Severity
Critical	Highest — surfaced first
High
Medium
Low
Info	Lowest

Auto-ticketing

Critical and high become tickets

A Critical or High alert automatically raises a ticket, routed to the matching organisation, with its priority mapped from the severity — so a down server is already a ticket in the queue before anyone refreshes a dashboard. Lower-severity alerts notify admins without creating ticket noise.

Working the queue

The Alerts view filters by severity, status (active vs resolved) and organisation, and headlines the count of active critical alerts so the room knows where things stand. Resolve an alert when it clears; the auto-created ticket follows its own lifecycle.