Pulling refs/heads/main into main

_includes/admin/roles_log_observer.rst

@@ -17,13 +17,6 @@
     - Yes
     - Yes
 
-
-  * - :strong:`Live Tail`
-    - Yes
-    - Yes
-    - Yes
-    - Yes
-
   * - :strong:`Search and filter logs`
     - Yes
     - Yes
@@ -42,23 +35,17 @@
     - No
     - No
 
-  * - :strong:`View individual log details`
+  * - :strong:`View field aliases`
     - Yes
     - Yes
     - Yes
     - Yes
 
-  * - :strong:`Create and manage log processing rules`
+  * - :strong:`View individual log details`
     - Yes
     - Yes
-    - No
-    - No
-
-  * - :strong:`Apply processing rules across historical data`
     - Yes
     - Yes
-    - No
-    - No
 
   * - :strong:`Save and share Log Observer queries`
     - Yes
@@ -72,30 +59,6 @@
     - Yes
     - No
 
-  * - :strong:`Transform data with log processing rules`
-    - Yes
-    - Yes
-    - No
-    - No
-
-  * - :strong:`Create and manage log metricization rules`
-    - Yes
-    - Yes
-    - No
-    - No
-
-  * - :strong:`Create new S3 connection to allow infinite logging rules`
-    - Yes
-    - No
-    - No
-    - No
-
-  * - :strong:`Create and manage infinite logging rules`
-    - Yes
-    - Yes - after admin creates S3 connection
-    - No
-    - No
-
   * - :strong:`View org subscription usage`
     - Yes
     - No

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

@@ -32,7 +32,7 @@ Metrics pipeline management
 
 
 
-Log Observer and Log Observer Connect
+Log Observer Connect
 ===============================================================================
 
 

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

@@ -47,6 +47,8 @@ To add an SLI chart to a dashboard, follow these steps:
 #. Search for an existing dashboard or create a new dashboard.
 #. Select :strong:`OK` to add the SLI chart to the dashboard.
 
+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`.
+
 .. note:: You must have write permission for a dashboard to add an SLI chart to it.
 
 Troubleshooting with an SLI chart

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

@@ -139,7 +139,6 @@ To activate AlwaysOn Profiling, follow the steps for the appropriate programming
          -Dsplunk.profiler.enabled=true \
          -Dsplunk.profiler.memory.enabled=true \
          -Dotel.exporter.otlp.endpoint=http(s)://collector:4317 \
-         -Dsplunk.metrics.endpoint=http(s)://collector:9943
          -jar <your_application>.jar
 
       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

@@ -7,25 +7,26 @@ Export and share charts in Splunk Observability Cloud
 .. meta::
     :description: Share and export charts in Splunk Observability Cloud
 
-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.
+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.
 
 .. _exporting-chart-contents:
 
 Export chart contents
 ==========================
 
-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.
+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.
 
-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).
+* 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.
+* To export a chart from the dashboard view, select the chart actions menu (|more|) and select :guilabel:`Export chart as CSV`. 
 
-.. note:: List charts and table charts can't be exported because they don't have a data table.
+.. note:: You can only export SLI charts from the dashboard view.
 
 .. _sharing-a-chart:
 
 Share a chart
 ==================
 
-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.
+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.
 
 .. list-table::
    :header-rows: 1
@@ -38,46 +39,45 @@ The techniques available for sharing a chart depend on where you are viewing the
      - :strong:`Notes`
 
    * - In the Chart Builder
-     - Use the Share icon at top right or select :guilabel:`Share` from the chart's Actions menu (|more|)
+     - Use the Share icon at top right or select :guilabel:`Share` from the chart actions menu (|more|)
      - Version you are viewing, including any unsaved changes
      - 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`
-     - In most cases, can be viewed only by other users
+     - In most cases, only registered users can view
 
    * -
      - Copy the URL for the chart from your browser's address bar :strong:`(see important note below table)`
      - Most recently saved version
      - URL that links to the actual chart, which you can send to others or :ref:`pasting-chart-url-into-slack`
-     - Can be viewed only by other users
+     - Only registered users can view
 
    * -
      - Take a screenshot of the chart
      - Version you are viewing, including any unsaved changes
      - Provides a graphic representation of the chart
-     - Can be viewed by anyone
+     - Anyone can view
 
-   * - On a dashboard
+   * - In a dashboard
      - Select :guilabel:`Share` from the chart's Action menu (|more|)
      - Most recently saved version
      - 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`
-     - In most cases, can be viewed only by other users
+     - In most cases, only registered users can view
 
    * -
      - Right-click on the chart name and copy the link address :strong:`(see important note below table)`
      - Most recently saved version
      - URL that links to the actual chart, which you can send to others or :ref:`pasting-chart-url-into-slack`
-     - Can be viewed only by other users
+     - Only registered users can view
 
    * -
-     - Select :guilabel:`Download chart as image` from the chart's Actions menu
+     - Select :guilabel:`Download chart as image` from the chart actions menu (|more|)
      - Most recently saved version
      - Provides a graphic representation of the chart
-     - Can be viewed by anyone
-
+     - Anyone can view
    * -
      - Take a screenshot of the chart
      - Most recently saved version
      - Provides a graphic representation of the chart
-     - Can be viewed by anyone
+     - Anyone can view
 
 .. caution:: 
 
@@ -86,59 +86,56 @@ The techniques available for sharing a chart depend on where you are viewing the
 
 .. _share-feature-to-share:
 
-Use the Share feature to share a chart
+Use the share feature to share a chart
 ----------------------------------------------
 
 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.
 
-- 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|).
-
-- To share a chart you are viewing in a dashboard, select :guilabel:`Share` from the chart's Actions menu (|more|).
+- 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|).
 
-You'll see options for sharing, discussed below.
+- 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.
 
 .. _share-copy-directly-from-infra-monitoring:
 
-Share a copy directly from Infrastructure Monitoring
+Share a copy directly from Splunk Observability Cloud
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-You can send a copy of the chart to an email address or to any available third-party services (See :ref:`admin-notifs-index`.).
+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`.
 
 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.
 
 .. caution:: 
 
-
-   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.
+   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.
 
 .. _share-copy-using-a-link:
 
 Share a copy by using a link
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-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.
+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.
 
 .. _pasting-chart-url-into-slack:
 
 Paste a chart URL into Slack
 ---------------------------------
 
-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`.
+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`.
 
 Note the following regarding this feature.
 
-- 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`).
+- 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`.
 
 - The preview image has a standard size and is always displayed using the light theme.
 
-- The time zone is always represented as GMT (marked on the chart as UTC).
+- The time zone is always represented in UTC.
 
 .. note:: Troubleshooting
 
    If you don't see the preview image in Slack, possible reasons are:
 
-   - An administrator in your organization needs to upgrade the Slack integration (See: :ref:`slack`).
+   - An administrator in your organization needs to upgrade the Slack integration. For more information, see: :ref:`slack`.
 
-   - The channel you are pasting into isn't visible to the user who authorized the Slack integration in Infrastructure Monitoring.
+   - The channel you are pasting into isn't visible to the user who authorized the Slack integration in Splunk Observability Cloud.
 
    - Your Slack settings block link previews or block links sharing.

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

@@ -144,7 +144,6 @@ The following example shows how to activate the profiler using the system proper
    -Dsplunk.profiler.enabled=true \
    -Dsplunk.profiler.memory.enabled=true \
    -Dotel.exporter.otlp.endpoint=http(s)://collector:4318 \
-   -Dsplunk.metrics.endpoint=http(s)://collector:4318
    -jar <your_application>.jar
 
 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

@@ -98,7 +98,7 @@ To migrate your instrumentation to the version 2.5.0 or higher of the Java agent
    - Select :guilabel:`Data Migration`.
    - Inside the :guilabel:`Start migration` card, select :guilabel:`Start`.
 
-2. Turn on OTLP histograms in the Splunk Distribution of OpenTelemetry Collector.
+2. Turn on OTLP histograms in the Splunk Distribution of the OpenTelemetry Collector.
 
 
 

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

@@ -164,17 +164,21 @@ Make sure that you're using a valid Splunk access token when sending data direct
 Metrics exporter issues
 ===============================================================
 
-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:
+.. note:: See also :ref:`java-metrics-migration-guide`.
+
+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:
 
 To troubleshoot connectivity issues affecting application metrics, try the following steps:
 
-1. Make sure that ``splunk.metrics.endpoint`` points to the correct host.
+1. Make sure that you've removed the deprecated property ``splunk.metrics.endpoint`` from your configuration.
+
+2. Check that the OpenTelemetry Collector is configured and running.
 
-2. Check that the OpenTelemetry Collector or Smart Agent instance is configured and running.
+  * If you're using the :ref:`otlp-receiver`, make sure it points to the correct host/endpoint, for example ``http://<host>:4318/v1/metrics``.
 
-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``.
+  * If you're using the :ref:`signalfx-receiver`, make sure it points to ``http://<host>:4318/v2/datapoint``.
 
-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`.
+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`.
 
 
 .. _java-profiler-issues:

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

@@ -55,11 +55,11 @@ See the following table for a list of changes:
     * - Version 1.x name
       - Version 2.0 name
       - Description
-    * - `splunk-py-trace`, `splk-py-trace`
-      - `opentelemetry-instrument`
+    * - ``splunk-py-trace``, ``splk-py-trace``
+      - ``opentelemetry-instrument``
       - Activates the Splunk OpenTelemetry Python agent and sends traces and metrics to Splunk Observability Cloud. 
-    * - `splunk-py-trace-bootstrap`, `splk-py-trace-bootstrap`
-      - `opentelemetry-bootstrap`
+    * - ``splunk-py-trace-bootstrap``, ``splk-py-trace-bootstrap``
+      - ``opentelemetry-bootstrap``
       - Installs instrumentation libraries and dependencies for Splunk OpenTelemetry Python.
 
 .. _python-2.x-new-functions:
@@ -77,8 +77,8 @@ See the following table for new function names in Python 2.0:
     * - Version 1.x name
       - Version 2.0 name
       - Description
-    * - `start_tracing()`, `start_metrics()`
-      - `init_splunk_otel()`
+    * - ``start_tracing()``, ``start_metrics()``
+      - ``init_splunk_otel()``
       - Configures tracing, metrics, and logs for Splunk OpenTelemetry Python.
 
 .. _python-2.x-troubleshooting:

gdi/opentelemetry/components/signalfx-receiver.rst

@@ -9,7 +9,7 @@ SignalFx receiver
 
 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.
 
-.. 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`.
+.. note:: For information on the SignalFx exporter, see :ref:`signalfx-exporter`.
 
 The SignalFx receiver accepts: