Closed kaiyan-sheng closed 2 months ago
Pinging @elastic/obs-ds-hosted-services (Team:obs-ds-hosted-services)
Test list-metrics
API, which is the one uses include_linked_accounts
config parameter:
aws cloudwatch list-metrics --namespace AWS/RDS --metric-name CPUUtilization --region eu-west-3 --profile elastic-observability --recently-active PT3H --include-linked-accounts --dimensions Name=DBClusterIdentifier
and
aws cloudwatch list-metrics --namespace AWS/RDS --metric-name CPUUtilization --region eu-west-3 --profile elastic-observability --recently-active PT3H --no-include-linked-accounts --dimensions Name=DBClusterIdentifier
returns the same result.
Will test with metricbeat directly next.
latency=10m
just to make sure metric collection does not get impacted by latency. Keepinclude_linked_accounts = false
and here are the metrics you can see from Kibana:We only see metrics from 2 RDS instances.
include_linked_accounts = true
, save the policy and here are the metrics you can see from Kibana:We can see metrics from all 5 RDS instances.
These RDS instances are all from the same AWS account, cross account monitoring is not enabled either.
include_linked_accounts
should not affect the results.