removing references to deleted LO docs

Tracey Carter · Tracey Carter · commit f6502027c925 · 2024-10-01T17:30:18.000-07:00
diff --git a/admin/references/data-retention.rst b/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:
 
diff --git a/admin/subscription-usage/subscription-usage-overview.rst b/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>`
diff --git a/apm/apm-scenarios/troubleshoot-business-workflows.rst b/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`.
diff --git a/apm/apm-scenarios/troubleshoot-tag-spotlight.rst b/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`. 
diff --git a/gdi/get-data-in/gdi-guide/additional-resources.rst b/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`
diff --git a/gdi/get-data-in/get-data-in.rst b/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.
 
diff --git a/get-started/o11y.rst b/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.
 
diff --git a/infrastructure/monitor/hosts.rst b/infrastructure/monitor/hosts.rst
@@ -12,7 +12,7 @@ You can monitor host metrics with Splunk Observability Cloud. Before you can sta
 - :ref:`get-started-linux`
 - :ref:`get-started-windows`
 
-Splunk Observability Cloud provides infrastructure monitoring capabilities powered by the :ref:`Splunk Distribution of OpenTelemetry Collector <otel-intro>`. If you're also exporting logs from hosts and want to learn about how to view logs in Splunk Observability Cloud, see :ref:`get-started-logs`.
+Splunk Observability Cloud provides infrastructure monitoring capabilities powered by the :ref:`Splunk Distribution of OpenTelemetry Collector <otel-intro>`.
 
 You can also export and monitor data related to hosts, as described in the following table.
 
diff --git a/infrastructure/monitor/k8s-nav.rst b/infrastructure/monitor/k8s-nav.rst
@@ -158,9 +158,6 @@ The Analyzer displays overrepresented metrics properties for known conditions, s
 
 Next steps
 =====================
-
-If you're also exporting logs from Kubernetes and want to learn about how to view logs in Splunk Observability Cloud, see :ref:`get-started-logs`.
-
 You can also export and monitor data related to your Kubernetes clusters, as described in the following table.
 
 .. list-table::
diff --git a/infrastructure/monitor/k8s.rst b/infrastructure/monitor/k8s.rst
@@ -12,7 +12,7 @@ Monitor Kubernetes (classic version)
 
 Before you can start monitoring any Kubernetes resources, :ref:`get-started-k8s`, and log in with your administrator credentials.
 
-You can monitor Kubernetes metrics with Splunk Observability Cloud. Splunk Observability Cloud uses the Splunk Distribution of OpenTelemetry Collector for Kubernetes to provide robust infrastructure monitoring capabilities. If you're also exporting logs from Kubernetes and want to learn about how to view logs in Splunk Observability Cloud, see :ref:`get-started-logs`.
+You can monitor Kubernetes metrics with Splunk Observability Cloud. Splunk Observability Cloud uses the Splunk Distribution of OpenTelemetry Collector for Kubernetes to provide robust infrastructure monitoring capabilities.
 
 You can also export and monitor data related to your Kubernetes clusters, as described in the following table.
 
diff --git a/logs/intro-logconnect.rst b/logs/intro-logconnect.rst
@@ -21,7 +21,7 @@ Region and version availability
 
 What can I do with Log Observer Connect?
 ==============================================================
-The following table lists features available to customers who have integrated Splunk Enterprise or Splunk Cloud Platform with Log Observer, allowing them to use Log Observer Connect. If you have a Log Observer entitlement in Splunk Observability Cloud, see :ref:`get-started-logs` for a complete list of Log Observer features.
+The following table lists features available to customers who have integrated Splunk Enterprise or Splunk Cloud Platform with Splunk Observability Cloud, allowing them to use Log Observer Connect.
 
 .. list-table::
    :header-rows: 1
diff --git a/logs/lo-transition.rst b/logs/lo-transition.rst
@@ -17,9 +17,7 @@ The following sections explain how to achieve all logging pipeline features in S
 
 Log processing rules
 ---------------------------------------------------------------------------------------------
-You can continue using existing log processing rules. You can turn your existing log processing rules off and on. However, you cannot create new log processing rules or edit existing rules.
-
-Going forward, you can process data in the Splunk platform using the following methods:
+You can process data in the Splunk platform using the following methods:
 
 .. list-table::
    :header-rows: 1
@@ -44,55 +42,7 @@ Going forward, you can process data in the Splunk platform using the following m
      - See :new-page:`Use the Data Stream Processor <https://docs.splunk.com/Documentation/DSP/1.4.2/User/About>`.
 
 
-.. _transition-infinite-logging:
-
-Infinite logging rules
----------------------------------------------------------------------------------------------
-You can continue using existing infinite logging rules. See :ref:`logs-infinite` for more information. You can turn your existing infinite logging rules off and on. However, you cannot create new infinite logging rules or edit existing rules.
-
-Going forward, determine the best option for your organization by discussing with your Splunk representative the following types of data storage:
-
-.. list-table::
-   :header-rows: 1
-   :widths: 30, 40
-
-   * - :strong:`Storage type`
-     - :strong:`Documentation`
-
-   * - Dynamic Data Active Archive
-     - See :new-page:`Store expired Splunk Cloud Platform data in a Splunk-managed archive <https://docs.splunk.com/Documentation/SplunkCloud/9.0.2305/Admin/DataArchiver>`
-
-   * - Dynamic Data Self Storage
-     - See :new-page:`Store expired Splunk Cloud Platform data in your private archive <https://docs.splunk.com/Documentation/SplunkCloud/9.1.2308/Admin/DataSelfStorage>`
-   
-   * - Ingest actions
-     - See :new-page:`Use ingest actions to improve the data input process <https://docs.splunk.com/Documentation/SplunkCloud/latest/Data/DataIngest>`
-
-
-.. _transition-search-time-rules:
-
-Search-time processing rules
----------------------------------------------------------------------------------------------
-You cannot use search-time processing rules in the Log Observer Connect UI. Search-time rules are the application of log processing rules across historical data. See :ref:`logs-search-time-rules` for more information. 
-
-Going forward, you can utilize the following methods for processing data at search time in Splunk Cloud Platform:
-
-.. list-table::
-   :header-rows: 1
-   :widths: 30, 40
-
-   * - :strong:`Search-time processing method`
-     - :strong:`Documentation`
-
-   * - Field extractor
-     - See :new-page:`Build field extractions with the field extractor <https://docs.splunk.com/Documentation/SplunkCloud/latest/Knowledge/ExtractfieldsinteractivelywithIFX>`
-
-   * - Field aliases
-     - See :new-page:`Create field aliases in Splunk Web <https://docs.splunk.com/Documentation/SplunkCloud/9.0.2305/Knowledge/Addaliasestofields>`
-
-
-.. _transition-live-tail:
 
 Live Tail
 --------------------------------------------------------------------------------------------
-To achieve Live Tail functionalit, adjust the time range picker in the Splunk platform Search & Reporting app to :guilabel:`All time (real-time)` or :guilabel:`30 second window`. You must select :guilabel:`Search` again and rerun your search to see the most recent log events because live events do not stream in unprompted. For more information, see :new-page:`Select time ranges to apply to your search <https://docs.splunk.com/Documentation/SplunkCloud/9.1.2308/Search/Selecttimerangestoapply>`
+To achieve Live Tail functionality, adjust the time range picker in the Splunk platform Search & Reporting app to :guilabel:`All time (real-time)` or :guilabel:`30 second window`. You must select :guilabel:`Search` again and rerun your search to see the most recent log events because live events do not stream in unprompted. For more information, see :new-page:`Select time ranges to apply to your search <https://docs.splunk.com/Documentation/SplunkCloud/9.1.2308/Search/Selecttimerangestoapply>`
diff --git a/logs/save-share.rst b/logs/save-share.rst
@@ -11,7 +11,7 @@ Save and share Log Observer queries
 After you create useful queries in Log Observer, you can save them and share them with team members. You can only save or share queries on the :guilabel:`Splunk Observability Cloud data` index. A saved query is made up of a filter and any aggregations or search-time rules you applied during the search. You can only save a query if you have created a filter. Only customers with a Splunk Log Observer entitlement in Splunk Observability Cloud can save and share Log Observer queries.
 
 To learn how to create filters, see :ref:`logs-keyword`.
-Log Observer Connect has no default aggregation. Log Observer defaults to :guilabel:`All (*)`` logs grouped by :guilabel:`Severity`. To learn how to create a unique aggregation, see :ref:`logs-aggregations`. To learn how to create search-time rules, see :ref:`logs-search-time-rules`.
+Log Observer Connect has no default aggregation. Log Observer defaults to :guilabel:`All (*)`` logs grouped by :guilabel:`Severity`. To learn how to create a unique aggregation, see :ref:`logs-aggregations`. 
 
 .. note:: 
    All organizations have access to pre-defined queries for Kubernetes and Cassandra. These queries appear at the beginning of the list of saved queries and are a part of content packs. Content packs include pre-defined saved queries as well as log processing rules. Splunk Observability Cloud includes content packs for Kubernetes System Events and Cassandra.
