You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 2, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: sp-oncall/incidents/incident-pane.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ Incident Pane
30
30
Versions Supported: N/A (SaaS)
31
31
VictorOps Version Required: Standard andEnterprise
32
32
33
-
The Incident Pane serves as a repository for recent activities in your Timeline. The Incident Pane, located to the right of the Timeline, houses alerts that come into Splunk On-Call. We currently store seven days or 1,000 events worth of timeline alert history, whichever comes first. Historical data that fall outside of the aforementioned storage parameters of the Incident Pane may be obtained through the use of the :new-page:`VictorOps API <https://help.victorops.com/knowledge-base/api/>`.
33
+
The Incident Pane serves as a repository for recent activities in your Timeline. The Incident Pane, located to the right of the Timeline, houses alerts that come into Splunk On-Call. We currently store seven days or 1,000 events worth of timeline alert history, whichever comes first. Historical data that fall outside of the aforementioned storage parameters of the Incident Pane may be obtained through the use of the :ref:`spoc-api`.
:description: Splunk On-Call will contact you for triggered incidents using the below phone numbers and short code. You may add these numbers to your contacts in the Mobile App for both `Android <https://help.victorops.com/knowledge-base/android-devices-victorops/>`__ and `iOS <https://help.victorops.com/knowledge-base/ios-application/>`__ devices by navigating to *Settings >> Help and Support >>* *Add VictorOps to Your Contacts:*
8
+
:description: Splunk On-Call contacts you for triggered incidents using the following phone numbers and short code.
9
+
10
+
Splunk On-Call contacts you for triggered incidents using the following phone numbers and short code. To add these numbers to your contacts in the Splunk On-Call mobile app, go to :guilabel:`Settings` then :guilabel:`Help and Support` then :guilabel:`Add VictorOps to Your Contacts`. For more information about the Splunk On-Call mobile app, see :ref:`spoc-mobile-main`
:description: About the user roll in Splunk On-Call.
10
9
11
-
12
-
13
10
The goal of our Incident Frequency Report is to give your team the data and context around incidents to be proactive in your incident management response.
14
11
15
12
@@ -20,16 +17,12 @@ This integration is compatible with the following versions of Splunk On-Call:
20
17
21
18
- Enterprise
22
19
23
-
All users have the ability to reach out to Splunk On-Call support at any time with questions.
24
-
25
-
Live Chat: If you are logged into your Splunk On-Call instance, you will have the ability to Live Chat with the Splunk On-Call Support team.
26
20
27
-
While the Splunk On-Call Timeline gives you the real-time firehose to give your team full context during a firefight, our Incident Frequency Report allows your team to analyze the flow of incidents after the fact. Allowing you to go upstream to solve the incident causing the problem in your system.
21
+
While the Splunk On-Call Timeline gives you the real-time information to give your team full context during a firefight, use the incident frequency report to analyze the flow of incidents after the fact.
28
22
29
-
To access the Incident Frequency Report navigate to :guilabel:`Reports`, then :guilabel:`Incident Frequency`.
23
+
To access the Incident Frequency Report go to :guilabel:`Reports` then :guilabel:`Incident Frequency`.
30
24
31
-
32
-
Team Filtering
25
+
Team filtering
33
26
========================
34
27
35
28
Get a holistic overview of all incidents coming into Splunk On-Call by selecting the :guilabel:`All`, or take a deep dive into individual teams to uncover specific problem areas affecting your team.
@@ -48,9 +41,7 @@ Identifying the problem causing area is hard to pin down, so we give you the abi
48
41
:width:100%
49
42
:alt:There are four options to segment your incidents: integrations, host, service, or route key.
50
43
51
-
52
-
53
-
Date Range & Bucketing
44
+
Date range and bucketing
54
45
--------------------------
55
46
56
47
See how incident trends impact your team on a daily, weekly, or monthly basis. It's up to you how granular your scope can be.
@@ -59,8 +50,6 @@ See how incident trends impact your team on a daily, weekly, or monthly basis. I
59
50
:width:100%
60
51
:alt:Segment reports by date range.
61
52
62
-
63
-
64
53
Table view and hover state
65
54
-------------------------------
66
55
@@ -83,7 +72,7 @@ Things to note about the CSV:
83
72
- Timestamps are at millisecond granularity
84
73
- CSV is sorted by Incident ID in descending order
85
74
86
-
CSV File Column Headings
75
+
CSV file column headings
87
76
----------------------------------
88
77
89
78
When downloading the Incident Frequency CSV file you can expect to find the following columns to include the unit of time/timezone that the incident is recorded in. Time related column headings will appear in these formats:
Team routing keys are configured at the bottom of the Settings > Integrations page. For details, see `Routing Keys <http://help.victorops.com/knowledge-base/routing-keys/>`.
35
+
Team routing keys are configured at the bottom of the :guilabel:`Settings` then :guilabel:`Integrations`` page. For details, see :ref:`spoc-routing-keys`.
36
36
37
37
#. If you do not use routing, remove the *+$routing_key* part, including the plus sign, so that the email looks like this:
in your applications, letting you ship with confidence.
14
+
#. From the main timeline select :guilabel:`Integrations` then :guilabel:`BugSnag`.
15
+
#. If the integration has not yet been enabled, select :guilabel:`Enable Integration`. Copy the :guilabel:`Service API Key` to your clipboard.
16
+
#. Once you have copied the API key to your clipboard, select :guilabel:`Settings` then :guilabel:`Routing Keys` to find your routing key configuration. Decide which routing_key will be used with this integration and make sure it is associated to the correct teams. You might need to create a new key.Routing keys are case sensitive.
14
17
15
-
The following will guide you through the steps needed to send you
16
-
bugsnag “Team Notifications” into the Splunk On-Call timeline.
18
+
In BugSnag
19
+
==================
17
20
18
-
**In Splunk On-Call**
19
-
---------------------
20
-
21
-
From the main timeline select **Integrations** *>>* **BugSnag**
22
-
23
-
If the integration has not yet been enabled, click the “Enable Integration” button. Copy the “Service API Key” to your clipboard.
24
-
.. image1
25
-
26
-
Once you have copied the API key to your clipboard, click on *Settings
27
-
>> Routing Keys* page to find your routing key configuration. Decide
28
-
which routing_key will be used with this integration and make sure it is
29
-
associated to the correct team/s. (You may need to create a new key)
30
-
Routing keys are case sensitive.
31
-
32
-
.. image:: /_images/spoc/atatus2.png
33
-
:alt:atatus2
34
-
35
-
atatus2
36
-
37
-
**In Bugsnag**
38
-
--------------
39
-
40
-
From the main web client, go into Settings.
41
-
42
-
.. image:: /_images/spoc/bugsnag2.png
43
-
:alt:bugsnag2
44
-
45
-
bugsnag2
46
-
47
-
In settings, select **Team Notifications** and then **VictorOps**.
48
-
49
-
.. image:: /_images/spoc/bugsnag3.png
50
-
:alt:bugsnag3
51
-
52
-
bugsnag3
53
-
54
-
Setup the alert to notify based on the options provided, and then drop
Use the bi-directional integration between HipChat and Splunk On-Call to fight fires from either platform and never miss a beat. All messages entered in the Splunk On-Call timeline, including alerts, on-call changes, escalations and chats appear in the HipChat room, and vice versa.
5
5
6
-
**Splunk On-Call Version Required: Starter / Growth** for **Single Room,
7
-
Enterprise** for **Multi-Room**
8
-
9
-
**What you need to know: Multi-Room requires the Rules Engine and
10
-
Webhooks i.e. Splunk On-Call Enterprise**
11
-
12
-
[/ht_toggle]
13
-
14
-
This bi-directional integration between HipChat and Splunk On-Call
15
-
(formerly called VictorOps) allows you to fight fires from either
16
-
platform and never miss a beat. All messages entered in the Splunk
17
-
On-Call timeline, including alerts, on-call changes, escalations and
18
-
chats will appear in the HipChat room, and vice versa.
6
+
Requirements
7
+
==============
19
8
20
-
This article provides step by step instructions for setting up the
21
-
integration for a Single Room or Multi-Room configuration.
9
+
* Splunk On-Call required version: Starter or Growth for Single Room, Enterprise for Multi-Room
22
10
23
-
--------------
11
+
Use these step by step instructions to set up the integration for a Single Room or Multi-Room configuration.
24
12
25
-
**Single Room**
13
+
Single Room
26
14
===============
27
15
28
-
**In Splunk On-Call**
16
+
In Splunk On-Call
29
17
---------------------
30
18
31
-
In Splunk On-Call, select *Integrations >> Hipchat*\ **.**
19
+
#. In Splunk On-Call, select :guilabel:`Integrations` then :guilabel:`Hipchat`.
32
20
33
21
If the integration has not yet been enabled, click the *Enable
34
22
Integration* button to generate your endpoint URL. Be sure to replace
@@ -143,9 +131,8 @@ This will allow you to change the room_id and auth_token depending on
143
131
the type of alert. In the example we match on the routing key “devops”
Copy file name to clipboardExpand all lines: sp-oncall/spoc-integrations/icinga-integration.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -277,7 +277,7 @@ You need to link the timeout command to a directory that is in the path.
277
277
Icinga version 2 configuration
278
278
===================================
279
279
280
-
After going through the preceeding installation instructions for Icinga (or `Nagios <https://help.victorops.com/knowledge-base/victorops-nagios-integration/>`__), use the following steps to add the VictorOps plugin to your Icinga 2 instance.
280
+
After going through the preceding installation instructions for Icinga (orNagios see :ref:`nagios-spoc`), use the following steps to add the VictorOps plugin to your Icinga 2 instance.
281
281
282
282
You can find these steps in the README.md file in /opt/victorops/nagios_plugin/icinga2_conf
Copy file name to clipboardExpand all lines: sp-oncall/spoc-integrations/jenkins-integration.rst
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,8 +25,7 @@ This integration is compatible with the following versions of Splunk On-Call:
25
25
The remainder of this topic walks you through the Jenkins integration with Splunk On-Call.
26
26
27
27
.. note::
28
-
There are two Jenkins integrations, this one with Splunk On-Call, and the :new-page:`Jenkins Delivery Insights Integration <https://help.victorops.com/knowledge-base/victorops-jenkins2-integration/>`,
29
-
which sends notifications to the Timeline about build status.
28
+
There are two Jenkins integrations, this one with Splunk On-Call, and the Jenkins Delivery Insights Integration which sends notifications to the Timeline about build status. See :ref:`jenkins-delivery-spoc` to learn more.
0 commit comments