Skip to main content

How To Use Cost Attribution Tags Effectively

Suppose you wanted to know how much each of your services cost to run. Maybe they're all running on the same EC2 instances, so you can't just rely on the cost breakdown in AWS's Cost Explorer.

With Beakpoint Insights, if you add the service.name tag to each trace and span, you can group by that tag to see how much each service costs.

In this case, you see that the cart service is responsible for most of our costs. Graph showing costs grouped by service