Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.

Commit f7ebbe7

Browse files
Merge pull request #2462 from splunk/urbiz-OD6538-aws-managed-ts
[6538]: AWS-managed TS doc
2 parents e54ec59 + b2b7a92 commit f7ebbe7

File tree

8 files changed

+124
-7
lines changed

8 files changed

+124
-7
lines changed

_images/gdi/aws-ts-awsmanaged1.png

360 KB
Loading

_images/gdi/aws-ts-awsmanaged2.png

221 KB
Loading

_images/gdi/aws-ts-awsmanaged3.png

314 KB
Loading

_images/gdi/aws-ts-awsmanaged4.png

382 KB
Loading

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

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,12 @@ Troubleshoot your AWS integration
77
.. meta::
88
:description: Resolve AWS policy, permission conflicts, and other issues in Splunk Observability Cloud.
99

10-
If you experience difficulties when connecting Splunk Observability Cloud to your Amazon Web Services (AWS) account or using the platform, read on to troubleshoot common issues. See :ref:`aws-ts-metric-streams` for issues specific to Metric Streams.
10+
If you experience difficulties when connecting Splunk Observability Cloud to your Amazon Web Services (AWS) account or using the platform, read on to troubleshoot common issues.
11+
12+
See also the following docs:
13+
14+
* :ref:`aws-ts-metric-streams` for issues specific to Splunk-managed Metric Streams.
15+
* :ref:`aws-ts-ms-aws` for issues specific to AWS-managed Metric Streams.
1116

1217
If issues persist, you can also contact :ref:`support`.
1318

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

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,15 @@
11
.. _aws-ts-metric-streams:
22

33
******************************************************
4-
Troubleshoot AWS Metric Streams
4+
Troubleshoot Splunk-managed Metric Streams
55
******************************************************
66

77
.. meta::
88
:description: Troubleshoot AWS Metric Streams related issues.
99

1010
See the following topics when experiencing AWS Metric Streams related issues.
1111

12-
.. note::
13-
14-
See also :ref:`aws-troubleshooting`.
12+
.. note:: See also :ref:`aws-troubleshooting` and :ref:`aws-ts-ms-aws`.
1513

1614
I've enabled Splunk-managed Metric Streams in my AWS integration but I do not see any metrics streaming in
1715
==========================================================================================================
Lines changed: 113 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,113 @@
1+
.. _aws-ts-ms-aws:
2+
3+
******************************************************
4+
Troubleshoot AWS-managed Metric Streams
5+
******************************************************
6+
7+
.. meta::
8+
:description: Troubleshoot AWS-managed Metric Streams related issues.
9+
10+
See the following topics when experiencing AWS-managed Metric Streams related issues.
11+
12+
.. note:: See also :ref:`aws-troubleshooting` and :ref:`aws-ts-metric-streams`.
13+
14+
I've enabled AWS-managed Metric Streams in my AWS integration but I do not see any metrics streaming in
15+
==========================================================================================================
16+
17+
Log in to your AWS console and review the following:
18+
19+
Check the Metric Stream integration settings
20+
----------------------------------------------------------------------
21+
22+
In your CloudWatch console check the following:
23+
24+
* The :strong:`Errors` chart must show zero errors.
25+
26+
* The destination and output format must look similar to what is visible on the screenshot below. Note that your destination URL might use a different realm, for example https://ingest.us0.signalfx.com/v1/cloudwatch_metric_stream.
27+
28+
.. image:: /_images/gdi/aws-ts-awsmanaged1.png
29+
:width: 70%
30+
:alt: Metric Stream settings
31+
32+
Check the associated Firehose stream configuration
33+
----------------------------------------------------------------------
34+
35+
Go to your AWS console and check your Firehose stream configuration:
36+
37+
.. image:: /_images/gdi/aws-ts-awsmanaged2.png
38+
:width: 70%
39+
:alt: Firehose configuration
40+
41+
Check the associated Firehose stream metrics
42+
----------------------------------------------------------------------
43+
44+
Make sure that:
45+
46+
* :strong:`Incoming records` must have non-zero values.
47+
48+
* Note that if there's a low volume of traffic going through the stream, the value of ``IncomingRecords (per second average)`` can be significantly lower than ``RecordsPerSecondLimit``, and therefore it might look like there are no incoming records.
49+
50+
* :strong:`HTTP endpoint delivery success` must be 100%.
51+
52+
.. image:: /_images/gdi/aws-ts-awsmanaged3.png
53+
:width: 70%
54+
:alt: Firehose stream metrics
55+
56+
If there are any errors visible on the HTTP endpoint delivery success chart, update the Firehose stream destination settings to ensure that the HTTP endpoint is correct and use a new access token with INGEST scope.
57+
58+
* Note that your destination URL might use a different realm, for example https://ingest.us0.signalfx.com/v1/cloudwatch_metric_stream.
59+
60+
.. image:: /_images/gdi/aws-ts-awsmanaged4.png
61+
:width: 70%
62+
:alt: Destination settings
63+
64+
Review roles and permissions
65+
-----------------------------------
66+
67+
Check the following:
68+
69+
* Review the AWS role used by the Metric Streams.
70+
71+
* Make sure all required permissions are included, and that the CloudWatch metric stream region and the region listed in the AWS policy are the same.
72+
73+
* To find the AWS role used by the Metric Stream, go to the Stream overview page under the :strong:`Service Role to write to Amazon Data Firehose` label.
74+
75+
This is a sample AWS policy:
76+
77+
.. code-block:: none
78+
79+
{
80+
"Version": "2012-10-17",
81+
"Statement": [
82+
{
83+
"Effect": "Allow",
84+
"Action": [
85+
"firehose:PutRecord",
86+
"firehose:PutRecordBatch"
87+
],
88+
"Resource": [
89+
"arn:aws:firehose:eu-west-2:906383545488:deliverystream/PUT-HTP-7pH7O"
90+
]
91+
}
92+
]
93+
}
94+
95+
These are the trust relationships:
96+
97+
.. code-block:: none
98+
99+
{
100+
"Version": "2012-10-17",
101+
"Statement": [
102+
{
103+
"Effect": "Allow",
104+
"Principal": {
105+
"Service": "streams.metrics.cloudwatch.amazonaws.com"
106+
},
107+
"Action": "sts:AssumeRole"
108+
}
109+
]
110+
}
111+
112+
113+

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

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,12 +23,13 @@ Connect AWS to Splunk Observability Cloud
2323
Send AWS logs to Splunk Platform <aws-logs>
2424
Next steps <aws-post-install>
2525
Troubleshoot your AWS integration <aws-troubleshooting>
26-
Troubleshoot Metric Streams <aws-ts-metric-streams>
26+
Troubleshoot Splunk-managed Metric Streams <aws-ts-metric-streams>
27+
Troubleshoot AWS-managed Metric Streams <aws-ts-ms-aws>
2728
aws-recommended-stats.rst
2829
GetMetricStatistics API deprecation notice <aws-api-notice>
2930
aws-tutorial/about-aws-tutorial.rst
3031

31-
You have several data ingestion and connection methods when it comes to monitoring your Amazon Web Services (AWS) data in Splunk Observability Cloud.
32+
Splunk Observability Cloud offers you several data ingestion and connection methods to monitor your Amazon Web Services (AWS) data.
3233

3334
.. note:: If you want to send AWS data to the Splunk platform, use the Splunk add-on. Learn more at :new-page:`Splunk Add-on for AWS <https://docs.splunk.com/Documentation/AddOns/released/AWS/Description>`.
3435

0 commit comments

Comments
 (0)