Integrating Sazabi with VictorOps
Route Sazabi alerts to VictorOps (Splunk On-Call) for incident management and on-call scheduling.
Learn how to integrate Sazabi with VictorOps (Splunk On-Call) so you can route alerts directly to your on-call team and manage incidents through VictorOps.
About the Sazabi integration for VictorOps
The Sazabi integration for VictorOps routes alerts directly to VictorOps for incident management and on-call scheduling. When Sazabi detects issues in your telemetry data, alerts automatically create VictorOps incidents.
With the Sazabi integration for VictorOps, you can:
- Automatically create VictorOps incidents from Sazabi alerts.
- Map Sazabi alert severities to VictorOps message types (CRITICAL, WARNING, or INFO).
- Include relevant context like error messages and affected services in each incident.
- Link back to Sazabi for deeper investigation.
Prerequisites
Before you connect VictorOps, make sure you have:
- A Sazabi account. Request access at sazabi.com
- A VictorOps (Splunk On-Call) account with permission to manage integrations.
Installation
Get your VictorOps credentials
In VictorOps, you need two pieces of information:
- REST endpoint URL: Go to Integrations -> REST Generic to find your endpoint URL.
- API ID: Go to Integrations -> API tab to find your API ID.
Connect to VictorOps
Click + Add connection and enter your REST endpoint URL and API ID.
Configure severity mapping
Under Settings -> Integrations -> VictorOps, configure how Sazabi alert severities map to VictorOps message types.
How it works
Once connected, Sazabi sends alerts to VictorOps using the REST endpoint API. Each alert includes:
- Error messages and descriptions
- Affected services
- Links back to Sazabi for deeper investigation
Severity mapping lets you control which Sazabi alert severities create VictorOps incidents and at what message type:
- CRITICAL: For urgent issues requiring immediate attention
- WARNING: For issues that need attention but are not immediately critical
- INFO: For informational alerts