Skip to content

Commit f946949

Browse files
Adding the fix for the undefined labels. Merge branch 'main' of github.com:splunk/private-o11y-docs into trangl-o11ydocs-6987-detectors-payload-new-fields
2 parents 27fab4e + a301a28 commit f946949

29 files changed

+132
-1775
lines changed
Lines changed: 9 additions & 58 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
1-
name: Pull Request Reminder
1+
name: Heretto Update Reminder
22

33
on:
44
pull_request:
5-
types: [opened, synchronize, reopened]
5+
types: [opened, synchronize]
66

77
jobs:
88
reminder:
@@ -14,14 +14,13 @@ jobs:
1414
issues: write
1515
checks: write
1616
pull-requests: write
17-
steps:
18-
- name: Checkout code
19-
uses: actions/checkout@v4
2017

21-
- name: Get Pull Request Info
22-
id: pr_info
23-
uses: actions/github-script@v7
18+
19+
steps:
20+
- name: Add PR Comment
21+
uses: actions/github-script@v6
2422
with:
23+
github-token: ${{ secrets.MY_TOKEN }}
2524
script: |
2625
const { owner, repo, number } = context.issue;
2726
const pr = await github.rest.pulls.get({
@@ -31,58 +30,10 @@ jobs:
3130
});
3231
3332
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-
}
5633
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.`;
7034
await github.rest.issues.createComment({
7135
owner,
7236
repo,
7337
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-
});
38+
body: `@${author}, please make sure that you update the files in Heretto and post the Heretto share link in this PR.`
39+
})
1.46 MB
Loading
310 KB
Loading
141 KB
Loading

admin/authentication/SSO/sso.rst

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -75,6 +75,24 @@ Give your login service integration a name that your users recognize. On your cu
7575
this name appears in the button your users select to sign in. For example, use the name "Log in with Okta"
7676
for an Okta login service integration.
7777

78+
.. _default-sso-role:
79+
80+
.. raw:: html
81+
82+
<embed>
83+
<h2>Set up default SSO role</h2>
84+
</embed>
85+
86+
87+
When you set up SSO, the default role for a user signing in to Splunk Observability Cloud through SSO is the :guilabel:`power` role. You can change the default SSO role to any of the available roles in Splunk Observability Cloud.
88+
89+
To change the default SSO role, do the following:
90+
91+
1. Go to :guilabel:`Settings` then select :guilabel:`General Settings`.
92+
93+
2. In the :guilabel:`User Management` section, set a default role for SSO login by selecting a role from the drop-down list. The drop-down list defaults to the :guilabel:`power` role. The role you select becomes the role of any new user logging in through an SSO service. You can return to :guilabel:`General Settings` and update the default role for SSO login at any time.
94+
95+
7896
.. _multiple-integrations-sso:
7997

8098
.. raw:: html

apm/apm-spans-traces/service-map.rst

Lines changed: 3 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ See :ref:`apm-inferred-services` to learn more about inferred services in APM.
1515

1616
The following screenshot shows an example service map:
1717

18-
.. image:: /_images/apm/spans-traces/service-map-global-search-rename.png
18+
.. image:: /_images/apm/spans-traces/service-map-updated-view.png
1919
:width: 95%
2020
:alt: An example of the service map in Splunk APM Service Map.
2121

@@ -28,6 +28,8 @@ Use these steps to access the service map in Splunk APM:
2828
#. Log into Splunk Observability Cloud.
2929
#. Select :guilabel:`APM` in the navigation bar.
3030
#. Select :guilabel:`Service Map` on the APM landing page. The service map view opens, with the service map in the center.
31+
#. (Optional) Select :guilabel:`Switch to Classic Service Map` to switch to the lateral service map layout. The default constellation view displays a larger view of your environment and helps you quickly assess service performance.
32+
3133

3234
Using the service map, you can do the following:
3335

@@ -86,15 +88,6 @@ When configured, you can select tiles in the Related Content bar to seamlessly n
8688
.. image:: /_images/apm/spans-traces/service-map-related-content-global-search-rename.gif
8789
:alt: Using Related Content in Splunk Observability Cloud.
8890

89-
Configure and view global data links for your service map
90-
==========================================================
91-
92-
You can configure global data links to link Splunk APM properties, such as services, traces, spans, and span tags, to relevant resources. For example, you can link APM properties to Infrastructure Monitoring navigators and dashboards, Splunk instances, Kibana logs, Splunk AppDynamics tiers, or custom URLs.
93-
94-
For information on how to configure data links to display in your service map, see :ref:`apm-create-data-links`. You can also create a global data link directly from the APM :guilabel:`Service Map` by selecting an inferred service, selecting the :guilabel:`(⋯)` menu next to the inferred service name, and selecting :guilabel:`Configure data links`.
95-
96-
For information on how to view data links in your service map, see :ref:`apm-use-data-links`.
97-
9891
Share your view of the service map
9992
======================================
10093
To share your view of the service map with a colleague, copy and share the URL. Your current filter selections are preserved in the URL.

apm/apm-spans-traces/service-view.rst

Lines changed: 20 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ You can also access the service view for a specific service within the service m
2929

3030
Finally, you can also access the service view for a specific service by selecting the service from the APM landing page.
3131

32-
Use the service overview to monitor the health of your service
32+
Use the service view to monitor the health of your service
3333
=====================================================================
3434

3535
When you open the service view an environment is selected based on your recently viewed environments. Adjust the environment and time range filters if necessary. Use the following sections to monitor the health of your service.
@@ -54,6 +54,18 @@ Use the following metrics in the :guilabel:`Service metrics` section to monitor
5454
* Inferred services - un-instrumented third-party services
5555
* Pub/sub queues - Publisher/subscriber queues
5656

57+
Error breakdown
58+
-----------------
59+
60+
Use the following section to troubleshoot service errors and view relevant traces for specific error types. Select a point on the graph to view example traces for a particular data point, or select any value to hide the time series for that value.
61+
62+
.. image:: /_images/apm/spans-traces/service-view-errors.png
63+
:width: 95%
64+
:alt: Screenshot of charts on the service view page that display service errors.
65+
66+
* Errors by exception type - Displays errors with the span attribute ``exception.type``. Select a data point on the chart to view related traces and alert details for that time period.
67+
* Errors by status code - Displays errors based on the HTTP or gRPC error status code. Select a data point on the chart to view related traces and alert details for that selected time period and error. For more information about error status codes, see :new-page:`Semantic Conventions for HTTP Spans <https://opentelemetry.io/docs/specs/semconv/http/http-spans/>`.
68+
5769
Runtime metrics
5870
-----------------
5971

@@ -82,6 +94,13 @@ View Tag Spotlight view for your service
8294

8395
Select :guilabel:`Tag Spotlight` to view Tag Spotlight view filtered for your service. See :ref:`apm-tag-spotlight` to learn more about Tag Spotlight.
8496

97+
View errors for your service
98+
====================================================
99+
100+
Select the :guilabel:`Errors` tab to visualize errors for your service. Select a specific error type to view available traces for that error, and troubleshoot by viewing details such as the ``exception.message`` or ``exception.stacktrace``.
101+
102+
Administrators can pause these metrics by going to the :guilabel:`Sources of Errors MetricSets` section on the :guilabel:`APM MetricSets` page and selecting :guilabel:`Pause Indexing`. These metrics are turned on by default.
103+
85104
View endpoints for your service
86105
=================================
87106

apm/profiling/intro-profiling.rst

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -94,10 +94,7 @@ The following programming languages have instrumentation available:
9494
* :ref:`profiling-configuration-otel-dotnet`
9595
* - .NET (SignalFx)
9696
- SignalFx Instrumentation for .NET version 1.0.0 or higher
97-
98-
.NET versions 6.0 and higher are supported in AlwaysOn Profiling. .NET Framework is not supported.
99-
- * :ref:`instrument-dotnet-applications`
100-
* :ref:`profiling-configuration-dotnet`
97+
- .NET versions 6.0 and higher are supported in AlwaysOn Profiling. .NET Framework is not supported.
10198
* - Python (in beta)
10299
- Splunk Distribution of OpenTelemetry Python version 1.15 or higher
103100

apm/set-up-apm/troubleshoot-apm.rst

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,6 @@ If you have instrumented an application but are not seeing the relevant data in
1414
- :ref:`common-java-troubleshooting`
1515
- :ref:`common-python-troubleshooting`
1616
- :ref:`common-nodejs-troubleshooting`
17-
- :ref:`common-dotnet-troubleshooting`
1817
- :ref:`common-go-troubleshooting`
1918

2019
If the preceding steps don't help you resolve your instrumentation issues, contact :ref:`support`.

apm/span-tags/tag-spotlight.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ To view service performance broken down by your indexed span tags, follow these
2525
* Select the :guilabel:`Tag Spotlight` panel on the APM landing page or in the service map.
2626
* Select the :guilabel:`Tag Spotlight` tab in the service view for your service.
2727
* Use the search in the top toolbar to search for Tag Spotlight and select the navigation result to go to Tag Spotlight.
28-
#. Add time range, environment, workflow, service, operation, and tag filters as need to refine the data in your Tag Spotlight view. The default time range is for the last 15 minutes, and the data resolution is 10 seconds.
28+
#. Add time range, environment, workflow, service, endpoint, operation, and tag filters as need to refine the data in your Tag Spotlight view. The default time range is for the last 15 minutes, and the data resolution is 10 seconds.
2929
#. Use the request and errors and latency time-series charts at the top to see a distribution of your RED metrics.
3030
#. Use the bar charts under the request and errors and latency time-series charts to view RED metrics for each indexed span tag.
3131
#. View the distribution of all indexed span tags. The tag bar charts display either request and error distributions or latency distribution. Use the :guilabel:`Cards display` menu to select the data you want to display in the bars.

0 commit comments

Comments
 (0)