Merge branch 'main' into gschatz-O11YDOCS-6478

Author: gschatz-splunk

_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/application/span-attributes.rst

@@ -20,21 +20,21 @@ Semantic conventions
 
 The following semantic conventions apply for spans:
 
-- :new-page:`General <https://github.com/open-telemetry/semantic-conventions/blob/main/model/general.yaml>`: General semantic attributes that might be used in describing different kinds of operations.
+- :new-page:`General <https://github.com/open-telemetry/semantic-conventions/blob/main/docs/general/attributes.md>`: General semantic attributes that might be used in describing different kinds of operations.
 
-- :new-page:`HTTP <https://github.com/open-telemetry/semantic-conventions/blob/main/model/trace/http.yaml>`: For HTTP client and server spans.
+- :new-page:`HTTP <https://github.com/open-telemetry/semantic-conventions/blob/main/model/http/spans.yaml>`: For HTTP client and server spans.
 
-- :new-page:`Database <https://github.com/open-telemetry/semantic-conventions/blob/main/model/trace/database.yaml>`: For SQL and NoSQL client call spans.
+- :new-page:`Database <https://github.com/open-telemetry/semantic-conventions/blob/main/model/database/spans.yaml>`: For SQL and NoSQL client call spans.
 
-- :new-page:`RPC/RMI <https://github.com/open-telemetry/semantic-conventions/blob/main/model/trace/rpc.yaml>`: For remote procedure call (for example, gRPC) spans.
+- :new-page:`RPC/RMI <https://github.com/open-telemetry/semantic-conventions/blob/main/model/rpc/spans.yaml>`: For remote procedure call (for example, gRPC) spans.
 
-- :new-page:`Messaging <https://github.com/open-telemetry/semantic-conventions/blob/main/model/trace/messaging.yaml>`: For messaging system spans (queues, publish/subscribe, and so on).
+- :new-page:`Messaging <https://github.com/open-telemetry/semantic-conventions/blob/main/model/messaging/spans.yaml>`: For messaging system spans (queues, publish/subscribe, and so on).
 
-- :new-page:`FaaS <https://github.com/open-telemetry/semantic-conventions/blob/main/model/trace/faas.yaml>`: For Function as a Service (for example, AWS Lambda) spans.
+- :new-page:`FaaS <https://github.com/open-telemetry/semantic-conventions/blob/main/model/faas/spans.yaml>`: For Function as a Service (for example, AWS Lambda) spans.
 
-- :new-page:`Exceptions <https://github.com/open-telemetry/semantic-conventions/blob/main/model/trace/trace-exception.yaml>`: For recording exceptions associated with a span.
+- :new-page:`Exceptions <https://github.com/open-telemetry/semantic-conventions/blob/main/model/exceptions/events.yaml>`: For recording exceptions associated with a span.
 
-- :new-page:`Compatibility <https://github.com/open-telemetry/semantic-conventions/blob/main/model/trace/compatibility.yaml>`: For spans generated by compatibility components. For example, OpenTracing Shim layer.
+- :new-page:`Compatibility <https://github.com/open-telemetry/semantic-conventions/blob/main/model/opentracing/common.yaml>`: For spans generated by compatibility components. For example, OpenTracing Shim layer.
 
 Learn more about OpenTelemetry in the OpenTelemetry official documentation, such as library-specific semantic conventions for AWS Lambda, AWS SDK, or GraphQL.
 

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
 ------------------------------------------------------