Pulling refs/heads/main into main

_includes/gdi/available-aws.rst

@@ -88,7 +88,7 @@ You can collect data from the following AWS services:
     - :strong:`X`
     - 
     - 
-    - 
+    - :strong:`X`
 
   * - AWS/CloudFront
     - AWS CloudFront

admin/references/data-retention.rst

@@ -88,14 +88,6 @@ The following table shows the retention time period for each data type in APM.
      - 
        * 8 days
 
-.. _log-observer-data-retention:
-
-Data retention in Log Observer 
-============================================
-
-The retention period for indexed logs in Splunk Log Observer is 30 days. 
-
-
 .. _oncall-data-retention:
 
 Data retention in Splunk On-Call

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

@@ -5,7 +5,7 @@ Monitor and manage subscription usage and billing
 *********************************************************************
 
 .. meta::
-   :description: Monitor your Infrastructure Monitoring, APM, and Log Observer subscription usage. 
+   :description: Monitor your Splunk Observability Cloud subscription usage. 
 
 .. toctree::
    :hidden:

apm/db-query-perf/db-perf-troubleshooting.rst

@@ -55,7 +55,7 @@ If you are seeing database latency, but the query itself is not causing the issu
 * :ref:`microsoft-sql-server`
 * :ref:`postgresql`
 
-You can also use the Related Content tiles to pivot to Infrastructure Monitoring or Log Observer and further analyze database issues. See :ref:`get-started-relatedcontent` to learn more about Related Content.
+You can also use the Related Content tiles to pivot to Infrastructure Monitoring to further analyze database issues. See :ref:`get-started-relatedcontent` to learn more about Related Content.
 
 .. _disable-db-normalization:
 

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

@@ -20,14 +20,12 @@ To get data into Splunk APM AlwaysOn Profiling, you need the following:
 
 AlwaysOn Profiling is activated for all host-based subscriptions. For subscriptions based on traces analyzed per minute (TAPM), check with your Splunk support representative.
 
-.. note:: You don't need Log Observer to get data into Splunk APM AlwaysOn Profiling. See :ref:`exclude-log-data` for more information.
-
 .. _profiling-setup-helm:
 
 Helm chart deployments
 ---------------------------------------------------------------
 
-If you're deploying the Splunk Distribution of OpenTelemetry Collector using Helm, pass the following value when installing the chart:
+If you're deploying the Splunk Distribution of the OpenTelemetry Collector using Helm, pass the following value when installing the chart:
 
 .. code-block:: bash
 
@@ -43,7 +41,7 @@ You can also edit the parameter in the values.yaml file itself. For example:
    # If you don't use AlwaysOn Profiling for Splunk APM, you can disable it.
    profilingEnabled: false
 
-If you don't have a Log Observer entitlement and are using a version of the OTel Collector lower than 0.78.0, make sure to turn off logs collection:
+If you are using a version of the OTel Collector lower than 0.78.0, make sure to turn off logs collection:
 
 .. code-block:: yaml
 

data-visualization/dashboards/view-dashboards.rst

@@ -109,7 +109,7 @@ From the :strong:`Chart actions` menu, you can perform the following tasks:
 
 * Select :strong:`Troubleshoot from this Time Window (RUM)` to explore related data in Splunk RUM. (This option only exists if RUM contains data related to data in the logs chart.)
 
-* Select :strong:`Delete` to remove your logs chart from the dashboard. Deleting it from the dashboard does not impact the query you used to create your logs chart in Log Observer.
+* Select :strong:`Delete` to remove your logs chart from the dashboard. Deleting it from the dashboard does not impact the query you used to create it.
 
 Not all actions are available for all chart types.
 

gdi/get-data-in/connect/aws/aws-cloudformation.rst

@@ -9,6 +9,8 @@ Available CloudFormation and Terraform templates
 
 To create Splunk-managed Metric Streams resources you can either use :ref:`CloudFormation <aws-cloudformation-use>` or a :ref:`Terraform template <aws-terraform-use>`.
 
+.. note:: To collect logs, see :ref:`aws-logs`.
+
 .. _aws-cloudformation-use:
 
 Use CloudFormation to connect to Splunk Observability Cloud
@@ -24,8 +26,6 @@ To use CloudFormation to connect to Splunk Observability Cloud follow these step
 
 3. Select the QuickLink for your chosen template. The QuickLink automatically opens the AWS Management Console in the last region you used, but you can select any other region in the AWS Management Console.
 
-.. caution:: Splunk Log Observer is no longer available for new users. You can continue to use Log Observer if you already have an entitlement. To collect logs, see :ref:`aws-logs`.
-
 .. _aws-cloudformation-templates:
 
 Prepopulated CloudFormation templates

gdi/get-data-in/connect/aws/aws-logs.rst

@@ -11,5 +11,4 @@ Log collection is not available in Splunk Observability Cloud.
 
 Instead, you can use the Data Manager to send your AWS logs to Splunk Platform. Learn how at :new-page:`Onboard AWS in Data Manager <https://docs.splunk.com/Documentation/DM/1.8.2/User/AWSAbout>`. To query logs, use Log Observer Connect. See more at :ref:`logs-intro-logconnect`.
 
-If you have a Log Observer entitlement, you must transition to Splunk Cloud Platform or Splunk Enterprise. Read more at :ref:`lo-transition`.
 

gdi/get-data-in/connect/aws/aws-post-install.rst

@@ -35,7 +35,7 @@ Locate your metrics
 See your logs 
 ------------------------------------------------------
 
-Splunk Log Observer is no longer available for new users. You can continue to use Log Observer if you already have an entitlement. To collect logs, see :ref:`aws-logs`.
+To collect and visualize your logs, see :ref:`aws-logs`.
 
 Use Dashboards and Related Content
 ------------------------------------------------------

gdi/get-data-in/connect/azure/azure-logs-ingestion.rst

@@ -12,5 +12,4 @@ Log collection is not available in Splunk Observability Cloud.
 
 Instead, you can use the Data Manager to send your Azure logs to Splunk Platform. Learn how at :new-page:`Onboarding for Azure data in Data Manager <https://docs.splunk.com/Documentation/DM/1.8.2/User/StartConfigurationAzureAD>`. To query logs, use Log Observer Connect. See more at :ref:`logs-intro-logconnect`.
 
-If you have a Log Observer entitlement, you must transition to Splunk Cloud Platform or Splunk Enterprise. Read more at :ref:`lo-transition`.
 

gdi/get-data-in/connect/gcp/gcp-logs.rst

@@ -12,7 +12,6 @@ Log collection is not available in Splunk Observability Cloud.
 
 Instead, you can use the Data Manager to send your GCP logs to Splunk Platform. Learn how at :new-page:`Onboard GCP in Data Manager <https://docs.splunk.com/Documentation/DM/1.8.2/User/GCPAbout>`. To query logs, use Log Observer Connect. See more at :ref:`logs-intro-logconnect`.
 
-If you have a Log Observer entitlement, you must transition to Splunk Cloud Platform or Splunk Enterprise. Read more at :ref:`lo-transition`.
 
 
 

gdi/get-data-in/gdi-guide/apm/instrument-back-end.rst

@@ -35,7 +35,7 @@ After you've instrumented your application, you can access your data in the foll
 * The APM landing page
 * APM explorer view
 * Metric finder
-* Splunk Log Observer
+* Splunk Log Observer Connect
 
 Use one of these methods to make sure that your application data is reaching Splunk Observability Cloud.
 

gdi/get-data-in/gdi-guide/infrastructure/send-server-cluster-data.rst

@@ -10,7 +10,7 @@ Part 2: Install the OpenTelemetry Collector to send server and cluster data
 Install the :ref:`Splunk Distribution of OpenTelemetry Collector <otel-intro>` on any hosts or clusters you're using as a part of your infrastructure, such as servers running in your data center or on a virtual machine running in the cloud to: 
 
 - Send metrics to Infrastructure Monitoring
-- Send logs to Log Observer
+- Query logs in Log Observer Connect
 - Set up your environment to receive logs and traces from applications instrumented in :ref:`instrument-back-end-services-apm`.
 
 .. image:: /_images/infrastructure/k8s-nav-pivot.gif
@@ -87,10 +87,10 @@ You can find your infrastructure metrics by using the Splunk metric finder. For
 
 .. _query-logs-inframon:
 
-Query logs in Log Observer
+Query logs in Log Observer Connect 
 ----------------------------------------------------------------------------------------------
 
-If you chose to ingest logs, you can query them in the Splunk Log Observer. For more information, see :ref:`logs-timeline`.
+If you chose to ingest logs, you can query them in the Splunk Log Observer Connect. See more at :ref:`logs-intro-logconnect`.
 
 Next steps
 =========================================

gdi/opentelemetry/automatic-discovery/linux/linux-backend.rst

@@ -91,7 +91,7 @@ Using the installer script, you can install and activate automatic discovery for
                             curl -sSL https://dl.signalfx.com/splunk-otel-collector.sh > /tmp/splunk-otel-collector.sh && \
                             sudo sh /tmp/splunk-otel-collector.sh --with-instrumentation --realm <SPLUNK_REALM> -- <SPLUNK_ACCESS_TOKEN>
 
-                        .. note:: If you have a Log Observer entitlement or wish to collect logs for the target host, make sure Fluentd is installed and enabled in your Collector instance by specifying the ``--with-fluentd`` option.
+                        .. note:: If you wish to collect logs for the target host, make sure Fluentd is installed and enabled in your Collector instance by specifying the ``--with-fluentd`` option.
 
                         The system-wide automatic discovery method automatically adds environment variables to ``/etc/splunk/zeroconfig/java.conf``.
 
@@ -127,7 +127,7 @@ Using the installer script, you can install and activate automatic discovery for
 
                         The ``systemd`` instrumentation automatically adds environment variables to ``/usr/lib/systemd/system.conf.d/00-splunk-otel-auto-instrumentation.conf``.
 
-                        .. note:: If you have a Log Observer entitlement or wish to collect logs for the target host, make sure Fluentd is installed and enabled in your Collector instance by specifying the ``--with-fluentd`` option. 
+                        .. note:: If you wish to collect logs for the target host, make sure Fluentd is installed and enabled in your Collector instance by specifying the ``--with-fluentd`` option. 
 
                         To automatically define the optional ``deployment.environment`` resource attribute at installation time, run the installer script with the ``--deployment-environment <env>`` option. Replace ``<env>`` with the desired attribute value, for example, ``prod``, as shown in the following example:
 
@@ -232,7 +232,7 @@ Using the installer script, you can install and activate automatic discovery for
                                 curl -sSL https://dl.signalfx.com/splunk-otel-collector.sh > /tmp/splunk-otel-collector.sh && \
                                 sh /tmp/splunk-otel-collector.sh --with-instrumentation --realm <SPLUNK_REALM> -- <SPLUNK_ACCESS_TOKEN>
 
-                            .. note:: If you have a Log Observer entitlement or wish to collect logs for the target host, make sure Fluentd is installed and enabled in your Collector instance by specifying the ``--with-fluentd`` option. 
+                            .. note:: If you wish to collect logs for the target host, make sure Fluentd is installed and enabled in your Collector instance by specifying the ``--with-fluentd`` option. 
 
                         The system-wide automatic discovery method automatically adds environment variables to ``/etc/splunk/zeroconfig/node.conf``.
 
@@ -259,7 +259,7 @@ Using the installer script, you can install and activate automatic discovery for
 
                             The ``systemd`` automatic discovery method automatically adds environment variables to ``/usr/lib/systemd/system.conf.d/00-splunk-otel-auto-instrumentation.conf``.
 
-                            .. note:: If you have a Log Observer entitlement or wish to collect logs for the target host, make sure Fluentd is installed and enabled in your Collector instance by specifying the ``--with-fluentd`` option.
+                            .. note:: If you wish to collect logs for the target host, make sure Fluentd is installed and enabled in your Collector instance by specifying the ``--with-fluentd`` option.
 
                         You can activate AlwaysOn Profiling for CPU and memory, as well as metrics, using additional options, as in the following example:
 
@@ -311,7 +311,7 @@ Using the installer script, you can install and activate automatic discovery for
                             curl -sSL https://dl.signalfx.com/splunk-otel-collector.sh > /tmp/splunk-otel-collector.sh && \
                             sudo sh /tmp/splunk-otel-collector.sh --with-instrumentation --realm <SPLUNK_REALM> -- <SPLUNK_ACCESS_TOKEN>
 
-                        .. note:: If you have a Log Observer entitlement or wish to collect logs for the target host, make sure Fluentd is installed and enabled in your Collector instance by specifying the ``--with-fluentd`` option.
+                        .. note:: If you wish to collect logs for the target host, make sure Fluentd is installed and enabled in your Collector instance by specifying the ``--with-fluentd`` option.
 
                         The system-wide automatic discovery method automatically adds environment variables to ``/etc/splunk/zeroconfig/dotnet.conf``.
 
@@ -347,7 +347,7 @@ Using the installer script, you can install and activate automatic discovery for
 
                         The ``systemd`` instrumentation automatically adds environment variables to ``/usr/lib/systemd/system.conf.d/00-splunk-otel-auto-instrumentation.conf``.
 
-                        .. note:: If you have a Log Observer entitlement or wish to collect logs for the target host, make sure Fluentd is installed and enabled in your Collector instance by specifying the ``--with-fluentd`` option. 
+                        .. note:: If you wish to collect logs for the target host, make sure Fluentd is installed and enabled in your Collector instance by specifying the ``--with-fluentd`` option. 
 
                         To automatically define the optional ``deployment.environment`` resource attribute at installation time, run the installer script with the ``--deployment-environment <env>`` option. Replace ``<env>`` with the desired attribute value, for example, ``prod``, as shown in the following example:
 
@@ -563,9 +563,9 @@ Update automatic discovery and configuration
 
                 To manually upgrade the package:
 
-                1. Download the ``splunk-auto-auto-instrumentation`` Debian or RPM package for the target system from the :new-page:`GitHub Releases page <https://github.com/signalfx/splunk-otel-collector/releases>`.
+                3. Download the ``splunk-auto-auto-instrumentation`` Debian or RPM package for the target system from the :new-page:`GitHub Releases page <https://github.com/signalfx/splunk-otel-collector/releases>`.
 
-                2. Run the following commands to install the package. Replace ``<path to splunk-otel-auto-instrumentation deb/rpm>`` with the local path to the downloaded package:
+                4. Run the following commands to install the package. Replace ``<path to splunk-otel-auto-instrumentation deb/rpm>`` with the local path to the downloaded package:
 
                 .. tabs::
 

gdi/opentelemetry/collector-kubernetes/kubernetes-config-logs.rst

@@ -202,7 +202,7 @@ Collect Kubernetes events
 
 To see Kubernetes events as part of the :strong:`Events Feed` section in charts, set ``splunkObservability.infrastructureMonitoringEventsEnabled`` to ``true``. The cluster receiver will be configured with a Smart Agent receiver using the ``kubernetes-events`` monitor to send custom events.
 
-To collect Kubernetes events as logs for Log Observer or Log Observer Connect using the Collector, you need to add ``clusterReceiver.k8sObjects`` to your configuration file, and set ``logsEnabled`` to ``true`` in either ``splunkObservability`` or ``splunkPlatform``. Events are processed in the ``logs`` pipeline.
+To collect Kubernetes events as logs for Log Observer Connect using the Collector, you need to add ``clusterReceiver.k8sObjects`` to your configuration file, and set ``logsEnabled`` to ``true`` in either ``splunkObservability`` or ``splunkPlatform``. Events are processed in the ``logs`` pipeline.
 
 ``clusterReceiver.k8sObjects`` has the following fields:
 

gdi/opentelemetry/collector-linux/linux-config-logs.rst

@@ -18,7 +18,7 @@ Fluentd is turned off by default. If you already installed Fluentd on a host, re
 Collect Linux logs with Fluentd
 ===========================================================================
 
-If you have a Log Observer entitlement or want to collect logs for the target host with Fluentd, use the ``--with-fluentd`` option to also install Fluentd when installing the Collector. For example:
+If you want to collect logs for the target host with Fluentd, use the ``--with-fluentd`` option to also install Fluentd when installing the Collector. For example:
 
 .. code-block:: bash
 

gdi/opentelemetry/collector-windows/install-windows-msi.rst

@@ -163,7 +163,7 @@ Learn more about advanced configuration options (including Service Logging) usin
 Install Fluentd MSI for log collection
 ==================================================
 
-If you have a Log Observer entitlement or wish to collect logs for the target host, make sure Fluentd is installed and enabled in your Collector instance. 
+If you have a wish to collect logs for the target host, make sure Fluentd is installed and enabled in your Collector instance. 
 
 .. note:: You need to be an Admin to configure log collection with Fluentd.
 

gdi/opentelemetry/collector-windows/install-windows.rst

@@ -179,7 +179,7 @@ Use the Universal Forwarder to send logs to the Splunk platform. See more at :re
 Collect Windows logs with Fluentd
 ---------------------------------------
 
-If you have a Log Observer entitlement or wish to collect logs for the target host with Fluentd, use the ``with_fluentd = 1`` option to install and enable Fluentd when installing the Collector. For example:
+If you wish to collect logs for the target host with Fluentd, use the ``with_fluentd = 1`` option to install and enable Fluentd when installing the Collector. For example:
 
 .. code-block:: PowerShell
 

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/install-the-collector.rst

@@ -170,7 +170,7 @@ To collect logs with the Splunk Distribution of the OpenTelemetry Collector:
 * In Kubernetes environments, native OpenTelemetry log collection is supported by default. See more at :ref:`kubernetes-config-logs`.
 * For Linux and Windows environments (physical hosts and virtual machines), use the Universal Forwarder to send logs to the Splunk platform. See more at :ref:`collector-with-the-uf`.
 
-.. note:: If you have a Log Observer entitlement or wish to collect logs for the target host, install and enable Fluentd in your Collector instance. 
+.. note:: If you wish to collect logs for the target host, install and enable Fluentd in your Collector instance. 
 
 .. raw:: html