Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.

Commit 3576312

Browse files
author
Tracey Carter
committed
Merge branch 'main' into tcarter-defaultSSOrole
2 parents 55bc255 + b904f9a commit 3576312

File tree

14 files changed

+142
-67
lines changed

14 files changed

+142
-67
lines changed
Lines changed: 88 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,88 @@
1+
name: Pull Request Reminder
2+
3+
on:
4+
pull_request:
5+
types: [opened, synchronize, reopened]
6+
7+
jobs:
8+
reminder:
9+
runs-on: ubuntu-latest
10+
permissions:
11+
id-token: write
12+
contents: read
13+
actions: read
14+
issues: write
15+
checks: write
16+
pull-requests: write
17+
steps:
18+
- name: Checkout code
19+
uses: actions/checkout@v4
20+
21+
- name: Get Pull Request Info
22+
id: pr_info
23+
uses: actions/github-script@v7
24+
with:
25+
script: |
26+
const { owner, repo, number } = context.issue;
27+
const pr = await github.rest.pulls.get({
28+
owner,
29+
repo,
30+
pull_number: number,
31+
});
32+
33+
const author = pr.data.user.login;
34+
const createdAt = new Date(pr.data.created_at);
35+
const now = new Date();
36+
const diffInDays = Math.floor((now - createdAt) / (1000 * 60 * 60 * 24));
37+
const labels = pr.data.labels.map(label => label.name);
38+
39+
return { author, diffInDays, number, labels };
40+
41+
- name: Check if Reminder Needed
42+
id: check_reminder
43+
uses: actions/github-script@v7
44+
with:
45+
script: |
46+
const { diffInDays, labels } = ${{ steps.pr_info.outputs }};
47+
const reminderLabel = 'reminder sent';
48+
const daysThreshold = 1; // Number of days before sending reminder. Adjust as needed.
49+
50+
if (!labels) { // Check if labels is undefined or null
51+
return { sendReminder: diffInDays >= daysThreshold }; // send reminder if the time threshold is passed, even without labels.
52+
}
53+
if (labels.includes(reminderLabel)) {
54+
return { sendReminder: false };
55+
}
56+
57+
if (diffInDays >= daysThreshold) {
58+
return { sendReminder: true };
59+
} else {
60+
return { sendReminder: false };
61+
}
62+
63+
- name: Send Reminder Comment
64+
if: ${{ steps.check_reminder.outputs.sendReminder == 'true' }}
65+
uses: actions/github-script@v7
66+
with:
67+
script: |
68+
const { owner, repo, number, author } = ${{ steps.pr_info.outputs }};
69+
const message = `@${author}, please make sure that you update the files in Heretto and post the Heretto share link in this PR.`;
70+
await github.rest.issues.createComment({
71+
owner,
72+
repo,
73+
issue_number: number,
74+
body: message,
75+
});
76+
77+
- name: Add Reminder Label
78+
if: ${{ steps.check_reminder.outputs.sendReminder == 'true' }}
79+
uses: actions/github-script@v7
80+
with:
81+
script: |
82+
const { owner, repo, number } = ${{ steps.pr_info.outputs }};
83+
await github.rest.issues.addLabels({
84+
owner,
85+
repo,
86+
issue_number: number,
87+
labels: ['reminder sent'],
88+
});

gdi/get-data-in/application/otel-dotnet/instrumentation/manual-dotnet-instrumentation.rst

Lines changed: 13 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -31,17 +31,25 @@ To create custom spans and traces, follow these steps:
3131
3232
private static readonly ActivitySource RegisteredActivity = new ActivitySource("Examples.ManualInstrumentations.Registered");
3333
34-
4. Create an ``Activity``. Optionally, set tags:
34+
4. Create an ``Activity`` (Span). Optionally, set tags:
3535

3636
.. code:: csharp
3737
38-
using (var activity = RegisteredActivity.StartActivity("Main"))
38+
using (var activity = RegisteredActivity.StartActivity("Custom Span Name"))
3939
{
40-
activity?.SetTag("foo", "bar1");
41-
// your logic for Main activity
40+
// Check if the activity is sampled and if full data collection is enabled.
41+
// This ensures that tags and other custom attributes are only set when the activity is being recorded.
42+
// Note: Ensure that skipping logic based on sampling does not interfere with essential business operations.
43+
if(activity?.IsAllDataRequested)
44+
{
45+
// your logic for custom activity
46+
activity.SetTag("foo", "bar1");
47+
}
4248
}
4349
44-
4. Register your ``ActivitySource`` by setting the ``OTEL_DOTNET_AUTO_TRACES_ADDITIONAL_SOURCES`` environmental variable. You can set the value to either ``Examples.ManualInstrumentations.Registered`` or to ``Examples.ManualInstrumentations.*``, which registers the entire prefix.
50+
5. Register your ``ActivitySource`` by setting the ``OTEL_DOTNET_AUTO_TRACES_ADDITIONAL_SOURCES`` environmental variable. You can set the value to either ``Examples.ManualInstrumentations.Registered`` or to ``Examples.ManualInstrumentations.*``, which registers the entire prefix.
51+
52+
6. Invoke the action that generates an ``Activity``, note the trace ID of the ``Activity``, and locate the trace in Splunk APM. You should now see a span with the display name "Custom Span Name" in the trace tree.
4553

4654
See the :new-page:`OpenTelemetry official documentation <https://opentelemetry.io/docs/languages/net/instrumentation/#traces>` for additional information and examples.
4755

gdi/get-data-in/rum/browser/configure-rum-browser-instrumentation.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -200,7 +200,7 @@ The following example shows how to restrict sampling to logged in users:
200200
rumAccessToken: '<your_rum_token>',
201201
applicationName: '<application-name>',
202202
tracer: {
203-
sampler: shouldTrace ? new AlwaysOnSampler() : new SplunkRum.AlwaysOffSampler(),
203+
sampler: shouldTrace ? new SplunkRum.AlwaysOnSampler() : new SplunkRum.AlwaysOffSampler(),
204204
},
205205
});
206206
</script>

infrastructure/metrics-pipeline/use-case-archive.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ Actions
4141

4242
Kai decides to use Archived Metrics to control how Splunk Observability Cloud stores their team's data.
4343

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.
4545
#. 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.
4646
#. 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`.
4747
#. 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.

infrastructure/monitor/k8s-nav.rst

Lines changed: 11 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -64,8 +64,8 @@ The following table describes the Kubernetes navigators:
6464

6565
.. _k8s-nav-hierarchy-map:
6666

67-
Hierarchy map
68-
======================
67+
Investigate instances with the hierarchy map
68+
===============================================
6969

7070
.. note:: The hierarchy map is only available on the Kubernetes nodes, pods, and containers navigators.
7171

@@ -84,8 +84,10 @@ Nodes, pods, and containers are colored by health and status, as reported by Kub
8484
* Pods are colored by phase: ``Running``, ``Pending``, ``Succeeded``, ``Failed``, and ``Unknown``
8585
* Containers are colored by status: ``Ready``, ``Not Ready``, and ``Unknown``
8686

87-
Investigate instances in the hierarchy map
88-
---------------------------------------------
87+
Hierarchy map features
88+
------------------------
89+
90+
To investigate instances with the hierarchy map, use the following features:
8991

9092
* Breadcrumb navigation: Switch to different instances and jump across entity levels using the breadcrumb navigation bar.
9193
* Hover: Get more information about an instance, including its status or phase, by hovering over that instance.
@@ -94,15 +96,15 @@ Investigate instances in the hierarchy map
9496

9597
.. _k8s-nav-left-nav:
9698

97-
Left navigation panel
98-
============================
99+
Refine your view with the left navigation panel
100+
==================================================
99101

100-
Use the left navigation panel in the table or heat map view to quickly switch between Kubernetes entity types, search for filters, and access predefined filters.
102+
Use the left navigation panel in the table or heat map view to quickly switch between Kubernetes entity types, search for filters, use predefined filters, and view or use recently used filters.
101103

102-
To use the left navigation panel:
104+
To refine your view with the left navigation panel, use the following features:
103105

104106
* :guilabel:`Select entity type`: Use this drop-down menu to switch between Kubernetes entity types.
105-
* :guilabel:`Refine by`: Use this panel to search for filters or access a list of predefined filters. The list of predefined filters is searchable and organized by :guilabel:`Relationship` and :guilabel:`Attribute`.
107+
* :guilabel:`Refine by`: Use this panel to search for filters, use predefined filters, or view and use recently used filters. The list of predefined filters is searchable and organized by :guilabel:`Relationship` and :guilabel:`Attribute`.
106108

107109
.. _k8s-nav-analyzer-overview:
108110

sp-oncall/admin/get-started/team-dashboard.rst

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,23 @@
11
.. _team-dashboard:
22

33
************************************************************************
4-
Splunk On-Call
4+
Splunk On-Call team dashboard
55
************************************************************************
66

77
.. meta::
88
:description: Splunk On-Call system requirements, including browsers, mobile support, and incident requirements.
99

1010

1111

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.
1313

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.
1515

1616
Information Alerts can still be found on the Timeline Page.
1717

1818
.. image:: /_images/spoc/team-dashboard.png
1919
: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.
2121

2222

2323
Filters
@@ -44,12 +44,12 @@ Quickly identify responsible parties during a firefight by easily seeing which p
4444
Manual Incident Creation
4545
----------------------------
4646

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`.
4848

4949
Incident War Rooms
5050
----------------------------
5151

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>`.
5353

5454
People Table
5555
==================

sp-oncall/admin/sso/sp-sso-adfs.rst

Lines changed: 6 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -7,45 +7,28 @@ Configure Active Directory Federation Services Single Sign-On for Splunk On-Call
77
.. meta::
88
:description: Enable Splunk On-Call SSO for Active Directory Federation Services (ADFS) your organization.
99

10-
11-
12-
1310
Requirements
1411
==================
1512

1613
This integration is compatible with the following versions of Splunk On-Call:
1714

1815
- Full-Stack
1916

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>`.
2418

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
2620
complete the setup on the back-end and respond with confirmation.
2721

2822
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`.
2923

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-
4224
.. _sso-adfs-ac-spoc:
4325

26+
Configure SSO for Active Directory Federation Services (ADFS)
27+
==============================================================
4428

45-
Active Directory Federation Services (ADFS)
46-
===========================================================
29+
To configure SSO for Splunk On-Call using ADFS complete the following steps.
4730

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.
4932

5033
#. 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.
5134

sp-oncall/admin/sso/sp-sso-google.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ Configure Single Sign-On for Splunk On-Call using Google Apps
77
.. meta::
88
:description: Enable Splunk On-Call SSO for your organization.
99

10-
To configure SSO for Splunk On-Call using Google Apps:
10+
To configure SSO for Splunk On-Call using Google Apps complete the following steps.
1111

1212
#. Access the Admin portal for Google Apps and navigate to :guilabel:`Apps` then :guilabel:`SAML Apps`.
1313

sp-oncall/admin/sso/sp-sso-okta.rst

Lines changed: 2 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,6 @@ Configure Single Sign-On for Okta and Splunk On-Call
77
.. meta::
88
:description: Enable Splunk On-Call SSO for your organization.
99

10-
11-
12-
1310
Requirements
1411
==================
1512

@@ -20,20 +17,10 @@ This integration is compatible with the following versions of Splunk On-Call:
2017
To enable single sign-on (SSO) for your organization, you will need to provide an updated metadata file and your IDP. If you are
2118
interested in setting up SSO, please contact :ref:`Splunk On-Call Support <spoc-support>`.
2219

23-
24-
Administrator Setup
20+
Configure SSO for Okta
2521
==========================
2622

27-
Instructions to complete the SSO configuration with Splunk On-Call and your IDP are provided for:
28-
29-
- :ref:`sso-okta-spoc-setup`
30-
- :ref:`sso-google-spoc`
31-
-
32-
33-
.. _sso-okta-spoc-setup:
34-
35-
Okta
36-
==========
23+
To configure SSO for Okta complete the following steps.
3724

3825
#. From the Okta user homepage, select :guilabel:`Admin` to access the Okta Admin dashboard.
3926

sp-oncall/alerts/team-escalation-policy.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ Escalation policies determine set who is actually on-call for a given team and a
1111

1212
Some things to note:
1313

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.
1515
- 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`.
1616
- 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`.
1717

0 commit comments

Comments
 (0)