Azure App Service Plan
Required Azure App Service Plan Attributes
All of the following attributes are required for Beakpoint to calculate costs for traces originating from Azure App Service Plans.
| Attribute Name | Example Value | Allowed Values |
|---|---|---|
azure.asp.service_name | App Service | Azure service name |
azure.asp.location | eastus | Azure region |
azure.asp.sku_name | P1v3 | Azure App Service Plan SKU |
azure.asp.os_type | Linux | Linux, Windows |
azure.asp.instances | 2 | Number of instances |
Cost Calculation
Azure App Service Plans charge an hourly rate determined by the SKU and operating system. Beakpoint calculates the cost per span using its duration:
cost = hourly_rate × (span_duration_seconds / 3600)
Cost Allocation with Overlapping Spans
When multiple spans run concurrently on the same plan (identified by matching azure.asp.sku_name and azure.asp.os_type), Beakpoint proportionally allocates the hourly cost among all active spans. Each span pays its fraction of the hourly rate based on how long it ran. Spans on different plans (different SKU or OS) are priced independently.
Configuration Example
Set these attributes in your application's OpenTelemetry configuration:
OTEL_RESOURCE_ATTRIBUTES: "azure.asp.service_name=App Service,azure.asp.location=eastus,azure.asp.sku_name=P1v3,azure.asp.os_type=Linux,azure.asp.instances=2"
Missing Attributes
If any required attribute is missing, Beakpoint cannot calculate costs for that span. Ensure all five attributes are present in your instrumentation before sending traces.