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: infrastructure/metrics-pipeline/use-case-archive.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
@@ -41,7 +41,7 @@ Actions
41
41
42
42
Kai decides to use Archived Metrics to control how Splunk Observability Cloud stores their team's data.
43
43
44
-
#. In Splunk Observability Cloud, Kai goes to :guilabel:`Settings > Metrics Management`. In the :guilabel:`Pipeline Management` tab Kai searches for the metric ``service.latency`` and configures the ingestion route to Archived Metrics. Kai can now see all the MTS as Archived MTS.
44
+
#. In Splunk Observability Cloud, Kai goes to :guilabel:`Settings` then :guilabel:`Metrics Management`. In the :guilabel:`Pipeline Management` tab Kai searches for the metric ``service.latency`` and configures the ingestion route to Archived Metrics. Kai can now see all the MTS as Archived MTS.
45
45
#. Kai creates a route exception rule and specifies a filter where ``data_center_region = Europe``. This gives them the estimate of 2,497 Real-Time MTS. Kai also restores the previous hour data to make sure they don't have gaps.
46
46
#. Now, Kai views the list of charts and detectors that use ``service.latency``. To learn more about viewing or downloading the list, see :ref:`metrics-usage-report`.
47
47
#. Kai already had a filter set up on the charts and detectors for ``data_center_region = Europe``. Kai verifies the data is visible in one of the charts.
:description: Splunk On-Call system requirements, including browsers, mobile support, and incident requirements.
9
9
10
10
11
11
12
-
The Splunk On-Call provides a comprehensive overview of incidents. This view automatically defaults to the teams that you are a member of and allows teams to dive into the details and understand the status of alerts or incidents.
12
+
The Splunk On-Call provides a comprehensive overview of incidents. This view automatically defaults to the teams that you are a member of and allows teams to dive into the details and understand the status of alerts or incidents.
13
13
14
-
All incidents derived from integrated monitoring tools in the incident table include their respective logos to help you rapidly identify the source of an alert. Manually created incidents, along with incidents originating from the Email Endpoint or the REST API integrations, will remain logo free.
14
+
All incidents derived from integrated monitoring tools in the incident table include their respective logos to help you rapidly identify the source of an alert. Manually created incidents, along with incidents originating from the Email Endpoint or the REST API integrations, will remain logo free.
15
15
16
16
Information Alerts can still be found on the Timeline Page.
17
17
18
18
.. image:: /_images/spoc/team-dashboard.png
19
19
:width:100%
20
-
:alt:An image of the . On-Call individuals listed on the left; Team incidents are shown in the main pane.
20
+
:alt:An image of the team dashboard On-Call individuals listed on the left; Team incidents are shown in the main pane.
21
21
22
22
23
23
Filters
@@ -44,12 +44,12 @@ Quickly identify responsible parties during a firefight by easily seeing which p
44
44
Manual Incident Creation
45
45
----------------------------
46
46
47
-
You can create a manual incident from the by selecting :guilabel:`Create Incident` in the top right corner. For instructions, see :ref:`manual-incident`.
47
+
You can create a manual incident from the team dashboard by selecting :guilabel:`Create Incident` in the top right corner. For instructions, see :ref:`manual-incident`.
48
48
49
49
Incident War Rooms
50
50
----------------------------
51
51
52
-
Access Incident Details directly from the by selecting the incident number link. This will expand the incident and its event history in the :ref:`Incident War Room <war-room>`.
52
+
Access Incident Details directly from the team dashboard by selecting the incident number link. This will expand the incident and its event history in the :ref:`Incident War Room <war-room>`.
Copy file name to clipboardExpand all lines: sp-oncall/admin/sso/sp-sso-adfs.rst
+6-23Lines changed: 6 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,45 +7,28 @@ Configure Active Directory Federation Services Single Sign-On for Splunk On-Call
7
7
.. meta::
8
8
:description: Enable Splunk On-Call SSO for Active Directory Federation Services (ADFS) your organization.
9
9
10
-
11
-
12
-
13
10
Requirements
14
11
==================
15
12
16
13
This integration is compatible with the following versions of Splunk On-Call:
17
14
18
15
- Full-Stack
19
16
20
-
To enable single sign-on (SSO) for your organization, you will need to provide an updated metadata file and your IDP. If you are
21
-
interested in setting up SSO, please contact :ref:`Splunk On-Call Support <spoc-support>`.
22
-
23
-
17
+
To enable single sign-on (SSO) for your organization, you will need to provide an updated metadata file and your IDP. If you are interested in setting up SSO, please contact :ref:`Splunk On-Call Support <spoc-support>`.
24
18
25
-
Configure Single Sign On (SSO) between your Identity Provider (IDP) and Splunk On-Call. Our standard SSO setup uses SAML 2.0 protocol. As long as your IDP can use SAML 2.0 protocol, it can integrate with Splunk On-Call. The exact steps differ depending on which IDP you use, but the process typically involves exporting a .XML metadata file and sending it to our Support team. Once you have sent the .xml file, a Splunk On-Call support specialist will
19
+
Our standard SSO setup uses SAML 2.0 protocol. As long as your IDP can use SAML 2.0 protocol, it can integrate with Splunk On-Call. The exact steps differ depending on which IDP you use, but the process typically involves exporting a .XML metadata file and sending it to our Support team. Once you have sent the .xml file, a Splunk On-Call support specialist will
26
20
complete the setup on the back-end and respond with confirmation.
27
21
28
22
If your IDP does not have SAML capability, please contact Splunk On-Call Support to explore what alternative options may be available. For details on how to contact Splunk On-Call Support, see :ref:`spoc-support`.
29
23
30
-
31
-
Administrator Setup
32
-
==========================
33
-
34
-
Instructions to complete the SSO configuration with Splunk On-Call and your IDP are provided for:
35
-
36
-
- :ref:`sso-okta-spoc`
37
-
- :ref:`sso-google-spoc`
38
-
- :ref:`sso-onelogin-spoc`
39
-
- :ref:`sso-adfs-ac-spoc`
40
-
41
-
42
24
.. _sso-adfs-ac-spoc:
43
25
26
+
Configure SSO for Active Directory Federation Services (ADFS)
To configure SSO for Splunk On-Call using ADFS complete the following steps.
47
30
48
-
Once you have sent over your Metadata file, and the Splunk On-Call Support team has completed the configuration, you will receive an updated metadata file to complete the configuration on your side.
31
+
#. Once you have sent over your Metadata file and the Splunk On-Call Support team has completed the configuration, you will receive an updated metadata file to complete the configuration on your side.
49
32
50
33
#. In the ADFS Management console, navigate to :guilabel:`Trust Relationships`, then :guilabel:`Relying Party Trusts` and select :guilabel:`Add Relying Party Trust` in the :menuselection:`Actions` pane.
Copy file name to clipboardExpand all lines: sp-oncall/alerts/team-escalation-policy.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
@@ -11,7 +11,7 @@ Escalation policies determine set who is actually on-call for a given team and a
11
11
12
12
Some things to note:
13
13
14
-
- Only Team and Global Admins are able to make changes to Escalation Policies
14
+
- Only Team and Global Admins are able to make changes to Escalation Policies.
15
15
- Only users specified in the first step of an Escalation Policy will receive Timeline and Push notifications that they are on-call and will log hours in the on-call report as being on-call. If you would like users in subsequent steps of an escalation policy to receive these notifications and log these hours, see :ref:`multi-escalation-policies`.
16
16
- When an Escalation Policy is executed and a user is being notified, the user's personal paging policy determines how they will be contacted. See :ref:`custom-paging-policy`.
:description: Splunk On-Call contacts you for triggered incidents using the following phone numbers and short code.
9
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`
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`.
0 commit comments