More

Author: aurbiztondo-splunk

gdi/opentelemetry/components/fluentd-receiver.rst

@@ -69,4 +69,4 @@ For troubleshooting Fluentd, see:
 * :ref:`fluentd-collector-troubleshooting`
 * :ref:`otel-linux-uninstall-both-otel-and-tdagent`
 
-.. caution:: If you have a Log Observer entitlement or wish to collect logs for the target host with Fluentd, make sure Fluentd is installed and turned on in your Collector instance.
+.. caution:: If you wish to collect logs for the target host with Fluentd, make sure Fluentd is installed and turned on in your Collector instance.

gdi/opentelemetry/components/splunk-hec-exporter.rst

@@ -15,8 +15,6 @@ The exporter also sends AlwaysOn Profiling data to Splunk Observability Cloud. F
 
 For information about the HEC receiver, see :ref:`splunk-hec-receiver`.
 
-.. caution:: Splunk Log Observer is no longer available for new users. You can continue to use Log Observer if you already have an entitlement.
-
 Get started
 ======================
 
@@ -239,7 +237,7 @@ To turn off log collection for Splunk Observability Cloud while preserving Alway
      sourcetype: "otel"
      log_data_enabled: false
 
-If you need to turn off log data export to Splunk Observability Cloud, for example because you're using Log Observer Connect or because you don't have Log Observer in your organization, set ``log_data_enabled`` to ``false`` in the ``splunk_hec`` exporter of your Collector configuration file:
+If you need to turn off log data export to Splunk Observability Cloud, for example because you're using Log Observer Connect, set ``log_data_enabled`` to ``false`` in the ``splunk_hec`` exporter of your Collector configuration file:
 
 .. code-block:: yaml
    :emphasize-lines: 6

gdi/opentelemetry/smart-agent/smart-agent-migration-process.rst

@@ -167,7 +167,7 @@ Check for the following errors:
 
   * 429 (TOO MANY REQUESTS): Org is not provisioned for the amount of traffic being sent; reduce traffic or request increase in capacity
 
-  * 503 (SERVICE UNAVAILABLE): If using the Log Observer, this is the same as 429 (because that is how HECv1 responds). Otherwise, check the status page.
+  * 503 (SERVICE UNAVAILABLE): Check the status page.
 
 To confirm that a specific receiver is fetching metrics exposed by an application, update the configuration file, as shown in the following example.
 
@@ -198,7 +198,7 @@ If you are unable to determine the issue from logs, see :ref:`support`. Gather a
 
 .. _locate-sa-config-file:
 
-3. Locate your existing Smart Agent configuration file
+1. Locate your existing Smart Agent configuration file
 ================================================================
 
 The Smart Agent can be configured by editing the agent.yaml file. By default, the configuration is installed at ``/etc/signalfx/agent.yaml`` on Linux and ``\ProgramData\SignalFxAgent\agent.yaml`` on Windows. If you override the location while installing the Smart Agent using the ``-config`` command line flag, the configuration file is stored at the location that you specify.

get-started/o11y.rst

@@ -7,7 +7,7 @@ Get started with Splunk Observability Cloud
 .. meta::
     :description: Learn how to get started with Splunk Observability Cloud in five steps.
 
-This topic covers five high-level steps you can follow to get started with Splunk Observability Cloud and its products, which include Splunk Infrastructure Monitoring, Splunk Application Performance Monitoring (APM), Splunk Real User Monitoring (RUM), and Splunk Log Observer.
+This topic covers five high-level steps you can follow to get started with Splunk Observability Cloud and its products, which include Splunk Infrastructure Monitoring, Splunk Application Performance Monitoring (APM), Splunk Real User Monitoring (RUM), and Splunk Log Observer Connect.
 
 For an introduction to Splunk Observability Cloud products, see :ref:`welcome`.
 
@@ -29,7 +29,7 @@ Follow these steps to set up and make the most of Splunk Observability Cloud:
      - Cloud services, Servers, Server applications, Clusters, Applications, Serverless functions, User interfaces
 
    * - :ref:`get-started-explore` using: 
-     - Infrastructure Monitoring, Real User Monitoring, Log Observer, Application Performance Monitoring, Related Content
+     - Infrastructure Monitoring, Real User Monitoring, Log Observer Connect, Application Performance Monitoring, Related Content
 
    * - :ref:`get-started-customize`:
      - Detectors and alerts, Custom dashboards, Span tags, Business workflows, Logs pipeline, Custom data
@@ -75,7 +75,7 @@ Once you have data coming into Splunk Observability Cloud, it's time to do some
 
 - Use :ref:`Log Observer Connect <logs-intro-logconnect>` to pinpoint interesting log events and troubleshoot issues with your infrastructure and cloud services.
 
-- As described in step :ref:`get-started-gdi`, if you turned on :ref:`get-started-relatedcontent` when setting up your data integrations, you can select options in the Related Content bar to seamlessly navigate between APM, Log Observer, and Infrastructure Monitoring with your selected filters and context automatically applied to each view.
+- As described in step :ref:`get-started-gdi`, if you turned on :ref:`get-started-relatedcontent` when setting up your data integrations, you can select options in the Related Content bar to seamlessly navigate between APM, Log Observer Connect, and Infrastructure Monitoring with your selected filters and context automatically applied to each view.
 
 - Use the :ref:`mobile app <intro-to-mobile>` to check system critical metrics in Splunk Observability Cloud on the go, access real-time alerts with visualizations, and view mobile-friendly dashboards.
 

logs/keyword.rst

@@ -14,4 +14,4 @@ You can search for keywords, field names, or field values. To search your logs,
 
 .. include:: /_includes/logs/query-logs.rst
 
-When you add keywords, field names, or field values to the filters, Log Observer narrows the results in the Timeline and the Logs table so that only records containing the selected fields and values appear. To learn how you can reuse a productive search in the future, see :ref:`logs-save-share`.
+When you add keywords, field names, or field values to the filters, Log Observer Connect narrows the results in the Timeline and the Logs table so that only records containing the selected fields and values appear. To learn how you can reuse a productive search in the future, see :ref:`logs-save-share`.