splunk · aurbiztondo-splunk · Mar 26, 2025 · Mar 4, 2025 · Mar 15, 2025 · Mar 15, 2025
@@ -8,7 +8,13 @@
 
 2. In the content control bar, enter a time range in the time picker if you want to see logs from a specific historical period. To select a time range, you must select :guilabel:`Unlimited` from the :guilabel:`Search Records` field in step 5 below. When you select :guilabel:`150,000`, Log Observer returns only the most recent 150,000 logs regardless of the time range you select.
 
-3. Select :guilabel:`Index` next to :guilabel:`Saved Queries`, then select the indexes you want to query. When you do not select an index, Log Observer runs your query on all indexes to which you have access. If you want to search your Splunk platform (Splunk Cloud Platform or Splunk Enterprise) data, select the integration for the appropriate Splunk platform instance first, then select which index you want to query in Log Observer. You can query indexes from only one Splunk platform instance or Splunk Observability Cloud instance at a time. You can query Splunk platform indexes only if you have the appropriate role and permissions. 
+3. Select :guilabel:`Index` next to :guilabel:`Saved Queries`. In the pop-up window, first select a Splunk platform (Splunk Cloud Platform or Splunk Enterprise) connection in the :guilabel:`Connection selection` section. Then, in the :guilabel:`Index selection` section, select which index you want to query in Log Observer Connect. 
+
+   .. image:: /_images/logs/indexSelection.png
+            :width: 90%
+            :alt: The Log Observer index selection pop-up is displayed.
+
+.. note:: You can query indexes from only one Splunk platform instance at a time. You can query Splunk platform indexes only if you have the appropriate role and permissions in Splunk platform. 
 
 4. In the content control bar next to the index picker, select :guilabel:`Add Filter`. Select the :guilabel:`Keyword` tab to search on a keyword or phrase. Select the :guilabel:`Fields` tab to search on a field. Then press Enter. To continue adding keywords or fields to the search, select :guilabel:`Add Filter` again.
 
@@ -18,9 +24,11 @@
 
 7. Select :guilabel:`Run search`.
 
-8. Review the top values for your query on the the :guilabel:`Fields` panel on right. This list includes the count of each value in the log records. To include log records with a particular value, select the field name, then select ``=``. To exclude log records with a particular value from your results, select the field name, then select ``!=``. To see the full list of values and distribution for this field, select :guilabel:`Explore all values`.
+8. [Optional] If you want to stop the current search, select :guilabel:`Cancel search`. Partial results do  not display. To continue your search, select :guilabel:`Run search` again.
+
+9. Review the top values for your query on the the :guilabel:`Fields` panel on right. This list includes the count of each value in the log records. To include log records with a particular value, select the field name, then select ``=``. To exclude log records with a particular value from your results, select the field name, then select ``!=``. To see the full list of values and distribution for this field, select :guilabel:`Explore all values`.
 
-9. Optionally, if you are viewing Splunk platform data, you can open your query results in the Splunk platform and use SPL to further query the resulting logs. You must have an account in Splunk platform. To open the log results in the Splunk platform, select the :guilabel:`Open in Splunk platform` icon at the top of the Logs table. 
+10. [Optional] If you are viewing Splunk platform data, you can open your query results in the Splunk platform and use SPL to further query the resulting logs. You must have an account in Splunk platform. To open the log results in the Splunk platform, select the :guilabel:`Open in Splunk platform` icon at the top of the Logs table. 
 
    .. image:: /_images/logs/lo-openinsplunk.png
          :width: 90%

@@ -75,6 +75,24 @@ Give your login service integration a name that your users recognize. On your cu
 this name appears in the button your users select to sign in. For example, use the name "Log in with Okta"
 for an Okta login service integration.
 
+.. _default-sso-role:
+
+.. raw:: html
+
+  <embed>
+    <h2>Set up default SSO role</h2>
+  </embed>
+
+
+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.
+
+To change the default SSO role, do the following:
+
+1. Go to :guilabel:`Settings` then select :guilabel:`General Settings`.
+
+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.
+
+
 .. _multiple-integrations-sso:
 
 .. raw:: html

@@ -15,7 +15,7 @@ See :ref:`apm-inferred-services` to learn more about inferred services in APM.
 
 The following screenshot shows an example service map: 
 
-..  image:: /_images/apm/spans-traces/service-map-global-search-rename.png
+..  image:: /_images/apm/spans-traces/service-map-updated-view.png
     :width: 95%
     :alt: An example of the service map in Splunk APM Service Map.
 
@@ -28,6 +28,8 @@ Use these steps to access the service map in Splunk APM:
 #. Log into Splunk Observability Cloud. 
 #. Select :guilabel:`APM` in the navigation bar. 
 #. Select :guilabel:`Service Map` on the APM landing page. The service map view opens, with the service map in the center. 
+#. (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. 
+
 
 Using the service map, you can do the following: 
 
@@ -86,15 +88,6 @@ When configured, you can select tiles in the Related Content bar to seamlessly n
 ..  image:: /_images/apm/spans-traces/service-map-related-content-global-search-rename.gif
     :alt: Using Related Content in Splunk Observability Cloud.
 
-Configure and view global data links for your service map
-==========================================================
-
-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.
-
-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`.
-
-For information on how to view data links in your service map, see :ref:`apm-use-data-links`.
-
 Share your view of the service map
 ======================================
 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.

@@ -29,7 +29,7 @@ You can also access the service view for a specific service within the service m
 
 Finally, you can also access the service view for a specific service by selecting the service from the APM landing page.
 
-Use the service overview to monitor the health of your service
+Use the service view to monitor the health of your service
 =====================================================================
 
 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
    *  Inferred services - un-instrumented third-party services
    *  Pub/sub queues - Publisher/subscriber queues
 
+Error breakdown
+-----------------
+
+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.
+
+..  image:: /_images/apm/spans-traces/service-view-errors.png
+    :width: 95%
+    :alt: Screenshot of charts on the service view page that display service errors. 
+
+* 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. 
+* 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/>`.
+
 Runtime metrics
 -----------------
 
@@ -82,6 +94,13 @@ View Tag Spotlight view for your service
 
 Select :guilabel:`Tag Spotlight` to view Tag Spotlight view filtered for your service. See :ref:`apm-tag-spotlight` to learn more about Tag Spotlight.
 
+View errors for your service
+====================================================
+
+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``. 
+
+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.
+
 View endpoints for your service
 =================================
 

@@ -94,10 +94,7 @@ The following programming languages have instrumentation available:
        * :ref:`profiling-configuration-otel-dotnet`
    * - .NET (SignalFx)
      - SignalFx Instrumentation for .NET version 1.0.0 or higher
-
-       .NET versions 6.0 and higher are supported in AlwaysOn Profiling. .NET Framework is not supported. 
-     - * :ref:`instrument-dotnet-applications`
-       * :ref:`profiling-configuration-dotnet`
+     - .NET versions 6.0 and higher are supported in AlwaysOn Profiling. .NET Framework is not supported. 
    * - Python (in beta)
      - Splunk Distribution of OpenTelemetry Python version 1.15 or higher
 

@@ -14,7 +14,6 @@ If you have instrumented an application but are not seeing the relevant data in
 - :ref:`common-java-troubleshooting`
 - :ref:`common-python-troubleshooting`
 - :ref:`common-nodejs-troubleshooting`
-- :ref:`common-dotnet-troubleshooting`
 - :ref:`common-go-troubleshooting`
 
 If the preceding steps don't help you resolve your instrumentation issues, contact :ref:`support`.
@@ -25,7 +25,7 @@ To view service performance broken down by your indexed span tags, follow these
      * Select the :guilabel:`Tag Spotlight` panel on the APM landing page or in the service map. 
      * Select the :guilabel:`Tag Spotlight` tab in the service view for your service.
      * Use the search in the top toolbar to search for Tag Spotlight and select the navigation result to go to Tag Spotlight.
-#. 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.
+#. 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.
 #. Use the request and errors and latency time-series charts at the top to see a distribution of your RED metrics.
 #. Use the bar charts under the request and errors and latency time-series charts to view RED metrics for each indexed span tag.
 #. 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. 

@@ -21,7 +21,6 @@ Instrument .NET applications for Splunk Observability Cloud (OpenTelemetry)
    Manual instrumentation <instrumentation/manual-dotnet-instrumentation>
    Performance overhead <performance>
    Troubleshoot the .NET instrumentation <troubleshooting/common-dotnet-troubleshooting>
-   SignalFx Instrumentation for .NET (Deprecated) TOGGLE <sfx/sfx-instrumentation>
    Migrate from SignalFx Instrumentation for .NET <troubleshooting/migrate-signalfx-dotnet-to-dotnet-otel>
 
 The Splunk Distribution of OpenTelemetry .NET provides zero-code instrumentation for popular .NET libraries and frameworks to collect and send telemetry to Splunk Observability Cloud.

@@ -180,8 +180,6 @@ Windows
 
 #. Check that you meet the requirements. See :ref:`dotnet-otel-requirements`.
 
-#. (Optional) If needed, uninstall the SignalFx Instrumentation for .NET. See :ref:`uninstall-dotnet-sfx`.
-
 #. Download and install the Splunk Distribution of OpenTelemetry .NET from the :new-page:`Releases page on GitHub <https://github.com/signalfx/splunk-otel-dotnet/releases>`. For example:
 
    .. code-block:: powershell
@@ -305,8 +303,6 @@ Linux
 
 #. Check that you meet the requirements. See :ref:`dotnet-otel-requirements`.
 
-#. (Optional) If needed, uninstall the SignalFx Instrumentation for .NET. See :ref:`uninstall-dotnet-sfx`.
-
 #. Download and install the installation script of the Splunk Distribution of OpenTelemetry .NET from the :new-page:`Releases page on GitHub <https://github.com/signalfx/splunk-otel-dotnet/releases>`. For example:
 
    .. code-block:: shell