Nagios integration
Integrate Nagios monitoring into ticket workflows to operationalize infrastructure alerts and automate incident response.
What it connects
- Current host and service status with last check time and state changes.
- Logical groupings of hosts and contacts for team-based routing and notifications.
- Scheduled downtime windows and acknowledged problems for context-aware alerting.
- Check commands and performance data from monitoring plugins for detailed incident triage.
What it automates
- Acknowledge infrastructure problems and suppress duplicate alerts from escalating further.
- Schedule maintenance windows and downtime periods to align monitoring with change activity.
- Trigger immediate checks on demand to verify resolution without waiting for the next scheduled scan.
- Disable and re-enable host notifications to control alert noise during temporary outages or planned work.
In practice
A Nagios check fails; STLabs creates a ticket with the exact failure message and triggers an immediate re-check to confirm the issue is not transient.
Your team schedules 2 hours of planned database maintenance; STLabs automatically schedules downtime in Nagios to prevent false alerts during the maintenance window.
A legacy server enters WARNING state; STLabs opens a ticket, adds a comment linking to the runbook, and automatically acknowledges the alert in Nagios to reduce noise.
Your incident commander needs to silence alerts for a subnet affected by a DDoS; STLabs disables notifications for affected hosts and creates an audit trail of when they will be re-enabled.
