Skip to content

Commit 6a384a9

Browse files
feedback
1 parent a79cfab commit 6a384a9

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

gdi/get-data-in/connect/aws/aws-ts-polling.rst

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -16,13 +16,13 @@ Calculate metric polling delay
1616

1717
Splunk Observability Cloud's CloudWatch data point sync consists of two phases:
1818

19-
1. ``list-metrics/`` time series sync
19+
1. Time series sync using the ``list-metrics`` API
2020

2121
* It syncs all time series (TS) active within the last 3 hours and stores time series info in Splunk Observability Cloud's internal storage.
2222

2323
* This sync runs every 15 minutes for each AWS integration. This interval is not configurable.
2424

25-
2. ``get-metric-data/`` data points sync
25+
2. Data points sync using the ``get-metric-data`` API
2626

2727
* It syncs all data points for all time series saved in Splunk Observability Cloud's internal storage.
2828

@@ -48,8 +48,6 @@ To minimize the number of requests for certain sparse metrics and reduce CloudWa
4848

4949
* Splunk Observability Cloud tried to retrieve data points for that specific metric using a lookback window of a maximum of 1 hour.
5050

51-
* The lookback window is computed as the highest value between the last known data point timestamp, or the request time minus 1 hour.
52-
5351
Example of sparse metrics lag
5452
----------------------------------------------------------------------
5553

0 commit comments

Comments
 (0)