Splunk > VictorOps Bi-Directional Integration
by Splunk
Maintain your incident and ticket history between ServiceNow and VIctorOps
Install Trend
View Install Data
| Date | Install Count | Change |
|---|---|---|
| 2026-09-09 | 0 | - |
| 134 days of no change | ||
| 2026-04-27 | 95 | -95 |
| 12 days of no change | ||
| 2026-04-14 | 96 | -1 |
| 6 days of no change | ||
| 2026-04-07 | 97 | -1 |
| 33 days of no change | ||
| 2026-03-04 | 98 | -1 |
| 32 days of no change | ||
| 2026-01-30 | 107 | -9 |
| 2 days of no change | ||
| 2026-01-27 | 108 | -1 |
| 1 days of no change | ||
| 2026-01-25 | 110 | -2 |
| 2026-01-24 | 112 | -2 |
| 2026-01-23 | 113 | -1 |
| 2026-01-22 | 116 | -3 |
| 2 days of no change | ||
| 2026-01-19 | 118 | -2 |
| 9 days of no change | ||
| 2026-01-09 | 120 | -2 |
| 1 days of no change | ||
| 2026-01-07 | 122 | -2 |
| 1 days of no change | ||
| 2026-01-05 | 123 | -1 |
| 1 days of no change | ||
| 2026-01-03 | 124 | -1 |
| 22 days of no change | ||
| 2025-12-11 | 125 | -1 |
| 1 days of no change | ||
| 2025-12-09 | 126 | -1 |
| 2025-12-08 | 127 | -1 |
| 35 days of no change | ||
| 2025-11-02 | 126 | +1 |
| 6 days of no change | ||
| 2025-10-26 | 125 | +1 |
| 11 days of no change | ||
| 2025-10-14 | 123 | +2 |
| 1 days of no change | ||
| 2025-10-12 | 122 | +1 |
| 16 days of no change | ||
| 2025-09-25 | 121 | +1 |
| 14 days of no change | ||
| 2025-09-10 | 120 | +1 |
| 56 days of no change | ||
| 2025-07-15 | 119 | +1 |
| 5 days of no change | ||
| 2025-07-09 | 118 | +1 |
| 120 days of no change | ||
| 2025-03-10 | 117 | +1 |
| 24 days of no change | ||
| 2025-02-13 | 116 | +1 |
| 26 days of no change | ||
| 2025-01-17 | 115 | +1 |
| 14 days of no change | ||
| 2025-01-02 | 114 | +1 |
About
VictorOps supports a DevOps-driven approach to incident response, with robust features to support proactive, collaborative resolutions. Basic on-call tools — including schedules and escalations — streamline notifications and expedite problem-solving. Customizable rules provide precise routing to minimize alerts from noisy systems and get the right person on the problem, quickly. Contextual alert information supports rapid remediation while user-first reports promote continuous learning. Native iOS and Android apps allow engineers to ack, resolve and reroute alerts from any device. Technical customer support and success are on-call to make everything from migration to configuration easy.
Installation Guide: https://help.victorops.com/knowledge-base/servicenow-bi-directional-integration-guide/
Key Features
The Splunk \> VictorOps Bi-Directional Integration maintains incident and ticket history but doesn’t distract you during a firefight. Leverage this detailed incident history to conduct thorough post-incident reviews and ensure on-call incident management gets better over time. Eliminate context-switching by working in a single application, focusing on the issue at hand and spending less time organizing tickets.
- Enterprise bidirectional integration: Create incidents in either Splunk On-Call or ServiceNow, keeping information up to date in both tools
- Simple onboarding: simplified onboarding to get teams up and running with ServiceNow and Splunk On-Call. Permissions and roles are scoped to the Splunk On-Call application within ServiceNow
- Communication across tools: worknotes and chat are kept up in sync across both ServiceNow and Splunk On-Call within incidents
- Intelligent routing: Direct incidents from ServiceNow using Assignment Groups and routing them to Splunk On-Call Escalation Policies
- Visibility across systems: Maintain custom and mandatory status fields across ServiceNow and Splunk On-Call including assignment groups, assigned to, etc.