Dogfooding the Billable Actions metric: How granular observability improved our metering validation

This post details how Temporal internally used the newly released Billable Actions metric and OpenMetrics endpoint to validate their metering pipeline. It describes the previous lack of granularity in the usage dashboard and how the new metric, broken down by `action_type` and `temporal_workflow_type`, allows for precise identification of cost drivers. The post highlights the internal use case of comparing direct Temporal Server queries with the emitted metric to debug discrepancies, leading to a more robust and efficient validation process. It also outlines the benefits for customers, including improved usage visibility, optimization opportunities, and validation capabilities.