You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cloudwatch recently added support for cross-account monitoring, which enables cloudwatch customers to setup a single 'monitoring account' which can access cloudwatch metrics from multiple other 'sharing accounts'.
Currently our AWS cloudwatch metrics integration does not support cross account metrics. Only metrics from the monitoring account itself are included when metric collection is configured.
In order to include metrics from linked sharing accounts, the IncludeLinkedAccounts parameter must be included in our ListMetrics API calls. The result of this is that the response contains metrics for the shared accounts as well as the monitoring account. The owning account is also listed for each returned metric, which will allow us to ensure that cloud.account.id is correct on all reported metrics.
The text was updated successfully, but these errors were encountered:
@andresrc we are testing the effects of having this on for non-cross-account scenarios, but if there are no additional side effects i don't see any problems with keeping it enabled.
Cloudwatch recently added support for cross-account monitoring, which enables cloudwatch customers to setup a single 'monitoring account' which can access cloudwatch metrics from multiple other 'sharing accounts'.
Currently our AWS cloudwatch metrics integration does not support cross account metrics. Only metrics from the monitoring account itself are included when metric collection is configured.
In order to include metrics from linked sharing accounts, the
IncludeLinkedAccounts
parameter must be included in our ListMetrics API calls. The result of this is that the response contains metrics for the shared accounts as well as the monitoring account. The owning account is also listed for each returned metric, which will allow us to ensure thatcloud.account.id
is correct on all reported metrics.The text was updated successfully, but these errors were encountered: