Pulling refs/heads/main into main

gdi/get-data-in/connect/aws/aws-ts-metric-streams.rst

@@ -28,6 +28,8 @@ If you're experiencing issues streaming metrics, check the following:
 
   * ``SplunkAccessToken`` needs to be a valid organization access token with ``INGEST`` authorization scope. You can find access tokens in the :strong:`Access Tokens` page in the Splunk Observability Cloud settings.
 
+* Make sure the tag ``splunk-metric-streams-firehose = <your_AWS_region>`` is present in your Kinesis Data Stream.
+
 * In the AWS Kinesis Streams console, validate that metrics are being delivered to the Kinesis Stream created by the CloudFormation template.
 
 * In the AWS S3 bucket used by Kinesis Firehose, check if there are any records that could not be delivered to Splunk Observability Cloud.

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

@@ -189,7 +189,7 @@ Learn more at :ref:`Costs for AWS monitoring <aws-costs>`.
 .. raw:: html
 
   <embed>
-    <h2>Install the Splunk Distribution of OpenTelemetry Collector<a name="install-splunk-otel-collector" class="headerlink" href="#install-splunk-otel-collector" title="Permalink to this headline">¶</a></h2>
+    <h2>Install the Splunk Distribution of the OpenTelemetry Collector<a name="install-splunk-otel-collector" class="headerlink" href="#install-splunk-otel-collector" title="Permalink to this headline">¶</a></h2>
   </embed>
 
 To take advantage of the full benefits of the Splunk Observability Cloud platform, install the :ref:`Splunk Distribution of the OpenTelemetry Collector <otel-intro>`.

infrastructure/monitor/aws-infra-import.rst

@@ -31,7 +31,7 @@ By default, Splunk Observability Cloud brings in data from all :ref:`supported A
 AWS data in Splunk Observability Cloud
 --------------------------------------------------------------------------------
 
-During import, Infrastructure Monitoring gives the metrics special names so you can identify them as coming from AWS: 
+During import, Splunk Observability Cloud gives the metrics special names so you can identify them as coming from AWS: 
 
 - AWS metadata becomes dimensions and custom properties. 
 - AWS tags are key-value pairs, so Infrastructure Monitoring converts them into custom properties.

infrastructure/monitor/aws.rst

@@ -20,7 +20,7 @@ Splunk Observability Cloud's Infrastructure Monitoring imports data, logs, and m
 
 To monitor AWS resources:
 
-1. Set up the Infrastructure Monitoring AWS integration. To learn more see :ref:`get-started-aws`.
+1. Set up the Splunk Observability Cloud AWS integration. To learn more see :ref:`get-started-aws`.
 2. :ref:`aws-infra-import`.
 3. Next, learn how to :ref:`monitor AWS with Splunk Observability Cloud <aws-infra-monitor>`.
 4. Finally, check :ref:`aws-infra-costs`.
@@ -97,7 +97,7 @@ Infrastructure Monitoring also sends a set of metrics for AWS related to errors
       <h2>Monitor AWS with the OpenTelemetry Collector<a name="aws-infra-otel" class="headerlink" href="#aws-infra-otel" title="Permalink to this headline">¶</a></h2>
    </embed>
 
-You can also use the Splunk Distribution of OpenTelemetry Collector to import AWS metrics and metadata. The Collector offers much more customization than you have available with the AWS integration, so you might want to use it when you want to see metrics at a finer resolution or when you need more control over the metrics you import. 
+You can also use the Splunk Distribution of the OpenTelemetry Collector to import AWS metrics and metadata. The Collector offers much more customization than you have available with the AWS integration, so you might want to use it when you want to see metrics at a finer resolution or when you need more control over the metrics you import. 
 
 You can only use the Collector when you have direct control over the applications installed on an AWS instance, such as AWS Elastic Compute Cloud (EC2). Some other AWS services require you to use Infrastructure Monitoring AWS integration and AWS CloudWatch. As a result, you might need to use both the AWS integration and OTel.