dd-audit-cost-spike-investigation

Datadog cost spike investigation works by correlating Usage Metering data with Audit Trail configuration changes to find the root cause. It links billing anomalies directly to specific configuration modifications, revealing exactly what triggered the usage increase.

Yes, you can find configuration changes causing a Datadog usage spike by correlating Usage Metering data with Audit Trail events. This pinpoints the exact timing of the spike and matches it with configuration modifications to identify the specific changes responsible.

To audit cost spikes for specific Datadog products like Logs or APM, you filter the Audit Trail configuration changes to target those products. This narrows the investigation to only the usage metering and changes relevant to the product experiencing the spike.

Yes, you need Usage Metering and Audit Trail data access to investigate Datadog billing spikes. The investigation workflow requires querying both datasets to correlate billing anomalies with configuration changes and identify the root cause.

The workflow for analyzing Datadog cost spike investigation results involves pinpointing the spike in Usage Metering, searching for related Audit Trail configuration changes, and analyzing the correlated results. This step-by-step process isolates the root cause of the cost spike.