Does AWS integration with filtering by tag have an impact on AWS billing or not?

[AurelienGravier]

Hello,

The use of AWS integration impacts Dynatrace license costs (DDU or DPS) but Amazon may also charge you extra for CloudWatch metric queries.

Without filtering on the Dynatrace side, I will get 4480 metrics per polling.
With tag filtering on resources that matter, I will get 483 metrics per polling.

The question is: Should I estimate Amazon costs based on 4480 metrics or 483 metrics?

That makes a slight difference on AWS billing 🤔 :
https://calculator.aws/#/createCalculator/CloudWatch

Tiered price for: 4,480 metrics
4,480 metrics x 0.30 USD = 1,344.00 USD
Total offer cost = 1,344.00 USD (Cost of metrics, including custom metrics)
CloudWatch metrics cost (monthly): 1,344.00 USD

Tiered price for: 483 metrics
483 metrics x 0.30 USD = 144.90 USD
Total offer cost = 144.90 USD (Cost of metrics, including custom metrics)
CloudWatch metrics cost (monthly): 144.90 USD

Thank you for your help.
Regards Aurelien

[jaume_reverte · Accepted solution]

Hello, 

Based on my testing of the connection, it will reduce the price you should expect. Filtering occurs directly on the AWS side, meaning we request less information, resulting in fewer metrics extracted and lower AWS costs.

An example of this filtering can be: "DimensionFilters": [ { "Name": "Environment", "Value": "Production" } ] in this case we are filtering to get only the entities with the tag Environment:Production.