Incident & on-call · Scale+ · Shipped V2.5
Everguardly + Splunk On-Call (VictorOps)
CRITICAL / RECOVERY events to Splunk On-Call.
Add Splunk On-Call (formerly VictorOps) as an alert channel and Everguardly posts a CRITICAL event when a monitor goes down and a RECOVERY event when it’s back, keyed by entity id so your on-call timeline stays correlated.
What you can do
- CRITICAL on down, RECOVERY on up
- Correlated entity id per incident
- REST endpoint encrypted at rest
Setup
Add a Splunk On-Call channel in Settings → Channels with a REST endpoint.
Add an alert channel →Frequently asked questions
- How do I connect Splunk On-Call (VictorOps) to Everguardly?
- Connect Splunk On-Call (VictorOps) from your Everguardly dashboard (or via the relevant setup guide). It takes a couple of minutes — you authenticate once, choose what fires, and Everguardly handles the rest. Available on the Scale plan and higher.
- Does the Splunk On-Call (VictorOps) integration cost extra?
- No. The Splunk On-Call (VictorOps) integration is included on the Scale plan and every plan above it — there is no separate integration fee. Every plan starts with a 14-day free trial, no credit card required.
- Is my Splunk On-Call (VictorOps) API token stored securely?
- Yes. Any credential you provide is encrypted at rest (AES-256-GCM) and decrypted only at the moment Everguardly needs to call Splunk On-Call (VictorOps). Tokens are never shown again after you connect and are never returned to the browser.
Connect Splunk On-Call (VictorOps) to Everguardly.
Start free in under a minute — Everguardly watches uptime, SSL and domains while Splunk On-Call (VictorOps) keeps your team in the loop.