Skip to main content

Supported Cost Attribution Tags

Beakpoint Insights supports the following cost attribution tags:

CategoryNameDescriptionExample
Resource / Deploymentdeployment.environment.nameDeployment environment name (e.g., staging, production, development).staging
Resource / FaaScloud.resource_idCloud provider-specific native identifier of the monitored cloud resource (e.g., an ARN on AWS)arn:aws:lambda:REGION:ACCOUNT:function:foo
Resource / Cloud Providercloud.providerName of the cloud provider (e.g. AWS, Azure, GCP)aws
Resource / Cloud Providercloud.regionName of the cloud provider region (e.g., us-east-1)us-east-1
Codecode.function.nameThe method or function fully-qualified name without arguments.com.example.MyHttpService.serveRequest
Resource / Serviceservice.nameLogical name of the service.Shoppingcart
Resource / Serviceservice.namespaceLogical grouping or business domain for the service (e.g., organizational or functional area)Shop
Resource / Serviceservice.versionThe version string of the service API or implementation.2.0.0
Userapp.user.idThe user id of the user who made the request3032
Userapp.user.org.idThe organization id of the user who made the request1234
cloud.resource_id is more than an attribution tag

cloud.resource_id is also required for CUR cost finalization: it is how Beakpoint Insights matches your spans to AWS Cost and Usage Report line items to replace provisional (list-price) costs with your actual billed costs. It must be set as an OpenTelemetry resource attribute. See the per-service requirements under Cost Calculation Tags.