Merge pull request #2361 from splunk/tcarter-OD6490-killLOdocs

tcarter-OD6490-killLOdocs

Author: tcarter-splunk

admin/references/data-retention.rst

@@ -87,7 +87,8 @@ The following table shows the retention time period for each data type in APM.
 Data retention in Log Observer 
 ============================================
 
-The retention period for indexed logs in Splunk Log Observer is 30 days. If you send logs to S3 through the Infinite Logging feature, then the data retention period depends on the policy you purchased for your Amazon S3 bucket. To learn how to set up Infinite Logging rules, see :ref:`logs-infinite`.
+The retention period for indexed logs in Splunk Log Observer is 30 days. 
+
 
 .. _oncall-data-retention:
 

admin/subscription-usage/subscription-usage-overview.rst

@@ -64,6 +64,6 @@ Learn more at :ref:`per-product-limits` and the following docs:
 
    * Data ingest can be limited at the source by Cloud providers. You can track this with the metric ``sf.org.num.<cloudprovidername>ServiceClientCallCountThrottles``.
 
-* :ref:`Log Observer Connect limits <lo-connect-limits>` and :ref:`Log Observer limits <logs-limits>`
+* :ref:`Log Observer Connect limits <lo-connect-limits>`
 
 * :ref:`System limits for Splunk RUM <rum-limits>`

apm/apm-scenarios/troubleshoot-business-workflows.rst

@@ -81,4 +81,4 @@ Learn more
 
 * For details about business workflows, see :ref:`apm-workflows`.
 * For details about using Related Content, see :ref:`get-started-relatedcontent`.
-* For more information about using Splunk Log Observer to detect the source of problems, see :ref:`get-started-logs`.
+* For more information about using Splunk Log Observer Connect to detect the source of problems, see :ref:`logs-intro-logconnect`.

apm/apm-scenarios/troubleshoot-tag-spotlight.rst

@@ -81,4 +81,4 @@ Learn more
 
 * For details about Tag Spotlight, see :ref:`apm-tag-spotlight`.
 * For details about using Related Content, see :ref:`get-started-relatedcontent`.
-* For more information about using Splunk Log Observer to detect the source of problems, see :ref:`get-started-logs`. 
+* For more information about using Splunk Log Observer Connect to detect the source of problems, see :ref:`logs-intro-logconnect`. 

gdi/get-data-in/application/otel-dotnet/sfx/instrumentation/connect-traces-logs.rst

@@ -159,7 +159,6 @@ The instrumentation uses the underscore character as separator for field names (
 - ``service_version`` to ``service.version``
 - ``deployment_environment`` to ``deployment.environment``
 
-See :ref:`logs-processors` for more information on how to define log transformation rules.
 
 ILogger
 -------------------------

gdi/get-data-in/gdi-guide/additional-resources.rst

@@ -36,5 +36,5 @@ See the following resources for more information about each component in Splunk
 
 - :ref:`get-started-apm`
 - :ref:`get-started-infrastructure`
-- :ref:`get-started-logs`
+- :ref:`logs-intro-logconnect`
 - :ref:`get-started-rum`

gdi/get-data-in/get-data-in.rst

@@ -21,7 +21,7 @@ Use Splunk Observability Cloud to achieve full-stack observability of all your d
 - :ref:`Splunk Infrastructure Monitoring <infrastructure-infrastructure>`
 - :ref:`Splunk Application Performance Monitoring (APM) <get-started-apm>`
 - :ref:`Splunk Real User Monitoring (RUM) <rum-gdi>`
-- :ref:`Splunk Log Observer <get-started-logs>` and :ref:`Log Observer Connect <logs-intro-logconnect>`
+- :ref:`Splunk Log Observer Connect <logs-intro-logconnect>`
 
 This guide provides four chapters that guide you through the process of setting up each component of Splunk Observability Cloud.
 

gdi/opentelemetry/data-processing.rst

@@ -117,7 +117,6 @@ See and manage logs
 
 To see and manage your logs, use :ref:`lo-connect-landing`.
 
-.. caution:: Splunk Log Observer is no longer available for new users. You can continue to use Log Observer if you already have an entitlement. Learn more in :ref:`logs-logs`.
 
 See and manage metrics
 ---------------------------------------

get-started/o11y.rst

@@ -73,7 +73,7 @@ Once you have data coming into Splunk Observability Cloud, it's time to do some
 
 - Use :ref:`RUM <get-started-rum>` to analyze the performance of web and mobile applications and keep track of how users are interacting with your front-end services, including page load times and responsiveness.
 
-- Use :ref:`Log Observer <get-started-logs>` or :ref:`Log Observer Connect <logs-intro-logconnect>` to pinpoint interesting log events and troubleshoot issues with your infrastructure and cloud services.
+- 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.
 
@@ -95,8 +95,6 @@ Now that you've explored and familiarized yourself with the data you have coming
 
 - Customize your APM experience by setting up business workflows and creating span tags that add metadata to traces sent to APM. For more information, see :ref:`apm-workflows` and :ref:`apm-add-context-trace-span`.
 
-- Customize your :ref:`logs pipeline <logs-pipeline>` to add value to your raw logs.
-
 
 .. _get-started-datalinks:
 

get-started/welcome.rst

@@ -107,10 +107,10 @@ For more information, see the :ref:`intro-synthetics`.
 
 .. _welcome-logobs:
 
-Splunk Log Observer
-===================
+Splunk Log Observer Connect 
+======================================
 
-Troubleshoot your application and infrastructure behavior using high-context logs in Splunk Observability Cloud. With Splunk Log Observer, you can perform codeless queries on logs to detect the source of problems in your systems. You can also extract fields from logs in Log Observer to set up log processing rules and transform your data as it arrives.
+Troubleshoot your application and infrastructure behavior using high-context logs in Splunk Observability Cloud. With Splunk Log Observer Connect, you can perform codeless queries on logs to detect the source of problems in your systems. 
 
 For more information, see :ref:`LogObserverFeatures`.