Getting the most out of the Billable Action Count metric

This post details practical ways to use the new `temporal_cloud_v1_billable_action_count` metric for cost analysis, debugging, and alerting. It explains what the metric is and isn't (usage estimates, not the bill; excludes certain actions; aggregated, not per execution). It provides PromQL queries for usage optimization analysis (identifying expensive Workflow Types and Action Types, combining dimensions, estimating total actions over 24 hours) and debugging (finding rare bugs via action type anomalies, spotting deployment regressions). It also offers alerting strategies for Action volume spikes relative to baseline, both at the Namespace and Workflow Type level.