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

Commit a9890da

Browse files
Merge branch 'main' into patch-1
2 parents c220d40 + 7831bca commit a9890da

File tree

11 files changed

+52
-88
lines changed

11 files changed

+52
-88
lines changed

_includes/admin/roles_log_observer.rst

Lines changed: 2 additions & 39 deletions
Original file line numberDiff line numberDiff line change
@@ -17,13 +17,6 @@
1717
- Yes
1818
- Yes
1919

20-
21-
* - :strong:`Live Tail`
22-
- Yes
23-
- Yes
24-
- Yes
25-
- Yes
26-
2720
* - :strong:`Search and filter logs`
2821
- Yes
2922
- Yes
@@ -42,23 +35,17 @@
4235
- No
4336
- No
4437

45-
* - :strong:`View individual log details`
38+
* - :strong:`View field aliases`
4639
- Yes
4740
- Yes
4841
- Yes
4942
- Yes
5043

51-
* - :strong:`Create and manage log processing rules`
44+
* - :strong:`View individual log details`
5245
- Yes
5346
- Yes
54-
- No
55-
- No
56-
57-
* - :strong:`Apply processing rules across historical data`
5847
- Yes
5948
- Yes
60-
- No
61-
- No
6249

6350
* - :strong:`Save and share Log Observer queries`
6451
- Yes
@@ -72,30 +59,6 @@
7259
- Yes
7360
- No
7461

75-
* - :strong:`Transform data with log processing rules`
76-
- Yes
77-
- Yes
78-
- No
79-
- No
80-
81-
* - :strong:`Create and manage log metricization rules`
82-
- Yes
83-
- Yes
84-
- No
85-
- No
86-
87-
* - :strong:`Create new S3 connection to allow infinite logging rules`
88-
- Yes
89-
- No
90-
- No
91-
- No
92-
93-
* - :strong:`Create and manage infinite logging rules`
94-
- Yes
95-
- Yes - after admin creates S3 connection
96-
- No
97-
- No
98-
9962
* - :strong:`View org subscription usage`
10063
- Yes
10164
- No

admin/user-management/roles/roles-and-capabilities-table.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ Metrics pipeline management
3232

3333

3434

35-
Log Observer and Log Observer Connect
35+
Log Observer Connect
3636
===============================================================================
3737

3838

alerts-detectors-notifications/slo/view-slo.rst

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -47,6 +47,8 @@ To add an SLI chart to a dashboard, follow these steps:
4747
#. Search for an existing dashboard or create a new dashboard.
4848
#. Select :strong:`OK` to add the SLI chart to the dashboard.
4949

50+
After adding an SLI chart to a dashboard, you can also save the chart as a CSV file or an image. For more information, see :ref:`export-and-share-charts`.
51+
5052
.. note:: You must have write permission for a dashboard to add an SLI chart to it.
5153

5254
Troubleshooting with an SLI chart

apm/profiling/get-data-in-profiling.rst

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -139,7 +139,6 @@ To activate AlwaysOn Profiling, follow the steps for the appropriate programming
139139
-Dsplunk.profiler.enabled=true \
140140
-Dsplunk.profiler.memory.enabled=true \
141141
-Dotel.exporter.otlp.endpoint=http(s)://collector:4317 \
142-
-Dsplunk.metrics.endpoint=http(s)://collector:9943
143142
-jar <your_application>.jar
144143
145144
For more configuration options, including setting a separate endpoint for profiling data, see :ref:`profiling-configuration-java`.

data-visualization/charts/export-and-share-charts.rst

Lines changed: 28 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -7,25 +7,26 @@ Export and share charts in Splunk Observability Cloud
77
.. meta::
88
:description: Share and export charts in Splunk Observability Cloud
99

10-
Infrastructure Monitoring provides a number of ways to `share a chart <sharing-a-chart_>`_ with someone else. The technique to use depends on several factors, such as the version you want to share (last saved version or version you are viewing that has unsaved changes) and whether you want to share the original or a copy.
10+
Splunk Observability Cloud provides a number of ways to export and share a chart. The technique to use depends on several factors, such as the version you want to share, last saved version or version you are viewing that has unsaved changes, and whether you want to share the original or a copy.
1111

1212
.. _exporting-chart-contents:
1313

1414
Export chart contents
1515
==========================
1616

17-
For line charts, area charts, and column charts, you can export the chart contents to a CSV file. The most recent 100 data points will be exported, along with the values of the dimensions associated with them.
17+
For line charts, area charts, column charts, and SLI charts, you can export the chart contents to a CSV file. The file contains the most recent 100 data points and the values of the dimensions associated with them.
1818

19-
To export a chart, first select :guilabel:`Data table` tab, next select :guilabel:`Export as CSV` download icon in the table headers row on the last column (the right side corner).
19+
* To export a chart from the Chart Builder view, open the :guilabel:`Data table` tab, then select :guilabel:`Export as CSV` download icon in the table headers row on the last column.
20+
* To export a chart from the dashboard view, select the chart actions menu (|more|) and select :guilabel:`Export chart as CSV`.
2021

21-
.. note:: List charts and table charts can't be exported because they don't have a data table.
22+
.. note:: You can only export SLI charts from the dashboard view.
2223

2324
.. _sharing-a-chart:
2425

2526
Share a chart
2627
==================
2728

28-
The techniques available for sharing a chart depend on where you are viewing the chart (on a dashboard or in the Chart builder). The following sections describe the various ways to share a chart.
29+
The techniques available for sharing a chart depend on where you are viewing the chart. The following sections describe the various ways to share a chart.
2930

3031
.. list-table::
3132
:header-rows: 1
@@ -38,46 +39,45 @@ The techniques available for sharing a chart depend on where you are viewing the
3839
- :strong:`Notes`
3940

4041
* - In the Chart Builder
41-
- Use the Share icon at top right or select :guilabel:`Share` from the chart's Actions menu (|more|)
42+
- Use the Share icon at top right or select :guilabel:`Share` from the chart actions menu (|more|)
4243
- Version you are viewing, including any unsaved changes
4344
- URL that links to a copy of the chart, which you can send to others (see :ref:`share-feature-to-share`) or :ref:`pasting-chart-url-into-slack`
44-
- In most cases, can be viewed only by other users
45+
- In most cases, only registered users can view
4546

4647
* -
4748
- Copy the URL for the chart from your browser's address bar :strong:`(see important note below table)`
4849
- Most recently saved version
4950
- URL that links to the actual chart, which you can send to others or :ref:`pasting-chart-url-into-slack`
50-
- Can be viewed only by other users
51+
- Only registered users can view
5152

5253
* -
5354
- Take a screenshot of the chart
5455
- Version you are viewing, including any unsaved changes
5556
- Provides a graphic representation of the chart
56-
- Can be viewed by anyone
57+
- Anyone can view
5758

58-
* - On a dashboard
59+
* - In a dashboard
5960
- Select :guilabel:`Share` from the chart's Action menu (|more|)
6061
- Most recently saved version
6162
- URL that links to a copy of the chart, which you can send to others (see :ref:`share-feature-to-share`) or :ref:`pasting-chart-url-into-slack`
62-
- In most cases, can be viewed only by other users
63+
- In most cases, only registered users can view
6364

6465
* -
6566
- Right-click on the chart name and copy the link address :strong:`(see important note below table)`
6667
- Most recently saved version
6768
- URL that links to the actual chart, which you can send to others or :ref:`pasting-chart-url-into-slack`
68-
- Can be viewed only by other users
69+
- Only registered users can view
6970

7071
* -
71-
- Select :guilabel:`Download chart as image` from the chart's Actions menu
72+
- Select :guilabel:`Download chart as image` from the chart actions menu (|more|)
7273
- Most recently saved version
7374
- Provides a graphic representation of the chart
74-
- Can be viewed by anyone
75-
75+
- Anyone can view
7676
* -
7777
- Take a screenshot of the chart
7878
- Most recently saved version
7979
- Provides a graphic representation of the chart
80-
- Can be viewed by anyone
80+
- Anyone can view
8181

8282
.. caution::
8383

@@ -86,59 +86,56 @@ The techniques available for sharing a chart depend on where you are viewing the
8686

8787
.. _share-feature-to-share:
8888

89-
Use the Share feature to share a chart
89+
Use the share feature to share a chart
9090
----------------------------------------------
9191

9292
You can share a copy of a chart. Copies include unsaved changes at the time you share, and autoexpire unless the recipient saves them. Sharing a copy is perfect for when you make a change that you want to show your team members, but don't want to modify the original chart.
9393

94-
- To share a chart you are viewing in the Chart Builder, select the :guilabel:`Share` icon near the upper right corner of the chart or select :guilabel:`Share` from the chart's Actions menu (|more|).
95-
96-
- To share a chart you are viewing in a dashboard, select :guilabel:`Share` from the chart's Actions menu (|more|).
94+
- To share a chart you are viewing in the Chart Builder, select the :guilabel:`Share` icon near the upper right corner of the chart or select :guilabel:`Share` from the chart actions menu (|more|).
9795

98-
You'll see options for sharing, discussed below.
96+
- To share a chart you are viewing in a dashboard, select :guilabel:`Share` from the chart actions menu (|more|). See the following sections for more information.
9997

10098
.. _share-copy-directly-from-infra-monitoring:
10199

102-
Share a copy directly from Infrastructure Monitoring
100+
Share a copy directly from Splunk Observability Cloud
103101
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
104102

105-
You can send a copy of the chart to an email address or to any available third-party services (See :ref:`admin-notifs-index`.).
103+
You can send a copy of the chart to an email address or to any available third-party services. To learn more, see :ref:`admin-notifs-index`.
106104

107105
After adding recipients, select :guilabel:`Share`. Recipients receive a link to the copy. When they open it, they can edit and save their copy without affecting the original.
108106

109107
.. caution::
110108

111-
112-
Administrators can add email addresses of people who aren't members of your organization. Recipients are to create a user account before they can view the shared content. Be sure the email addresses you enter for nonmembers are correct, especially if the item you are sharing contains any sensitive or proprietary information.
109+
Administrators can add email addresses of people who aren't members of your organization. Recipients must create a user account before they can view the shared content. Be sure the email addresses you enter for nonmembers are correct, especially if the item you are sharing contains any sensitive or proprietary information.
113110

114111
.. _share-copy-using-a-link:
115112

116113
Share a copy by using a link
117114
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
118115

119-
You might want to send out a personal email or post a link to the copy on an internal website. To do this, select :guilabel:`Copy`. Only members of your organization with a login will be able to see the chart you share.
116+
You might want to send out a personal email or post a link to the copy on an internal communication channel or website. To do this, select :guilabel:`Copy`. Only members of your organization with a login can see the chart you share.
120117

121118
.. _pasting-chart-url-into-slack:
122119

123120
Paste a chart URL into Slack
124121
---------------------------------
125122

126-
You can give someone access to a chart by pasting the chart's URL into a Slack channel; Slack displays a preview image of the chart along with the URL. You can paste a URL that was generated by using the Share feature or by copying the chart's URL, as described in :ref:`sharing-a-chart`.
123+
You can give someone access to a chart by pasting the chart's URL into a Slack channel. Slack displays a preview image of the chart along with the URL. You can paste a URL that was generated by using the Share feature or by copying the chart's URL, as described in :ref:`sharing-a-chart`.
127124

128125
Note the following regarding this feature.
129126

130-
- The preview image will appear in public channels, and in private channels or direct messages that are visible to the user who authorized the Slack integration (See: :ref:`slack`).
127+
- The preview image appears in public channels, private channels, and direct messages that are visible to the user who authorized the Slack integration. For more information, see: :ref:`slack`.
131128

132129
- The preview image has a standard size and is always displayed using the light theme.
133130

134-
- The time zone is always represented as GMT (marked on the chart as UTC).
131+
- The time zone is always represented in UTC.
135132

136133
.. note:: Troubleshooting
137134

138135
If you don't see the preview image in Slack, possible reasons are:
139136

140-
- An administrator in your organization needs to upgrade the Slack integration (See: :ref:`slack`).
137+
- An administrator in your organization needs to upgrade the Slack integration. For more information, see: :ref:`slack`.
141138

142-
- The channel you are pasting into isn't visible to the user who authorized the Slack integration in Infrastructure Monitoring.
139+
- The channel you are pasting into isn't visible to the user who authorized the Slack integration in Splunk Observability Cloud.
143140

144141
- Your Slack settings block link previews or block links sharing.

gdi/get-data-in/application/java/instrumentation/instrument-java-application.rst

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -144,7 +144,6 @@ The following example shows how to activate the profiler using the system proper
144144
-Dsplunk.profiler.enabled=true \
145145
-Dsplunk.profiler.memory.enabled=true \
146146
-Dotel.exporter.otlp.endpoint=http(s)://collector:4318 \
147-
-Dsplunk.metrics.endpoint=http(s)://collector:4318
148147
-jar <your_application>.jar
149148
150149
See :ref:`get-data-in-profiling` for more information. For more settings, see :ref:`profiling-configuration-java`.

gdi/get-data-in/application/java/migrate-metrics.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -98,7 +98,7 @@ To migrate your instrumentation to the version 2.5.0 or higher of the Java agent
9898
- Select :guilabel:`Data Migration`.
9999
- Inside the :guilabel:`Start migration` card, select :guilabel:`Start`.
100100

101-
2. Turn on OTLP histograms in the Splunk Distribution of OpenTelemetry Collector.
101+
2. Turn on OTLP histograms in the Splunk Distribution of the OpenTelemetry Collector.
102102

103103

104104

gdi/get-data-in/application/java/troubleshooting/common-java-troubleshooting.rst

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -164,17 +164,21 @@ Make sure that you're using a valid Splunk access token when sending data direct
164164
Metrics exporter issues
165165
===============================================================
166166

167-
If you see warnings about metrics in your logs, it might mean that the Java agent can't send metrics to your OTel Collector, Smart Agent (now deprecated), or to the Splunk platform endpoints:
167+
.. note:: See also :ref:`java-metrics-migration-guide`.
168+
169+
If you see warnings about metrics in your logs, it might mean that the Java agent can't send metrics to your OTel Collector instance or to the Splunk platform endpoints:
168170

169171
To troubleshoot connectivity issues affecting application metrics, try the following steps:
170172

171-
1. Make sure that ``splunk.metrics.endpoint`` points to the correct host.
173+
1. Make sure that you've removed the deprecated property ``splunk.metrics.endpoint`` from your configuration.
174+
175+
2. Check that the OpenTelemetry Collector is configured and running.
172176

173-
2. Check that the OpenTelemetry Collector or Smart Agent instance is configured and running.
177+
* If you're using the :ref:`otlp-receiver`, make sure it points to the correct host/endpoint, for example ``http://<host>:4318/v1/metrics``.
174178

175-
3. Check that the OpenTelemetry Collector or Smart Agent are using the correct ports for the SignalFx receiver. The Collector uses ``http://<host>:4318/v2/datapoint``, and the Smart Agent uses ``http://<host>:9080/v2/datapoint``.
179+
* If you're using the :ref:`signalfx-receiver`, make sure it points to ``http://<host>:4318/v2/datapoint``.
176180

177-
4. Make sure that you're using a valid Splunk access token when sending data directly to your Splunk platform instance. See :ref:`admin-api-access-tokens`.
181+
3. Make sure that you're using a valid Splunk access token when sending data directly to your Splunk platform instance. See :ref:`admin-api-access-tokens`.
178182

179183

180184
.. _java-profiler-issues:

gdi/get-data-in/application/python/migration-guide.rst

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -55,11 +55,11 @@ See the following table for a list of changes:
5555
* - Version 1.x name
5656
- Version 2.0 name
5757
- Description
58-
* - `splunk-py-trace`, `splk-py-trace`
59-
- `opentelemetry-instrument`
58+
* - ``splunk-py-trace``, ``splk-py-trace``
59+
- ``opentelemetry-instrument``
6060
- Activates the Splunk OpenTelemetry Python agent and sends traces and metrics to Splunk Observability Cloud.
61-
* - `splunk-py-trace-bootstrap`, `splk-py-trace-bootstrap`
62-
- `opentelemetry-bootstrap`
61+
* - ``splunk-py-trace-bootstrap``, ``splk-py-trace-bootstrap``
62+
- ``opentelemetry-bootstrap``
6363
- Installs instrumentation libraries and dependencies for Splunk OpenTelemetry Python.
6464

6565
.. _python-2.x-new-functions:
@@ -77,8 +77,8 @@ See the following table for new function names in Python 2.0:
7777
* - Version 1.x name
7878
- Version 2.0 name
7979
- Description
80-
* - `start_tracing()`, `start_metrics()`
81-
- `init_splunk_otel()`
80+
* - ``start_tracing()``, ``start_metrics()``
81+
- ``init_splunk_otel()``
8282
- Configures tracing, metrics, and logs for Splunk OpenTelemetry Python.
8383

8484
.. _python-2.x-troubleshooting:

gdi/opentelemetry/components/signalfx-receiver.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ SignalFx receiver
99

1010
The SignalFx receiver is a native OpenTelemetry component that allows the Splunk Distribution of the OpenTelemetry Collector to collect data in SignalFx proto format. Supported pipeline types are ``metrics`` and ``logs``. See :ref:`otel-data-processing` for more information.
1111

12-
.. note:: While the SignalFx Smart Agent has reached End of Support, OTel native components such as the Smart Agent receiver, the SignalFx receiver, and the SignalFx exporter are available and supported. For information on the exporter, see :ref:`signalfx-exporter`.
12+
.. note:: For information on the SignalFx exporter, see :ref:`signalfx-exporter`.
1313

1414
The SignalFx receiver accepts:
1515

0 commit comments

Comments
 (0)