Skip to main content
Spend alone doesn’t tell the whole story. Connect usage metrics to understand why costs changed and to what extent the change was driven by underlying business metrics.
Usage & Metrics

Support Matrix

Click a datasource to jump to the right setup steps.

CSV

  1. Prepare a CSV file in flat or columnar format.
    • Date column in YYYY-MM-DD
    • Metric values are numeric
  2. In Costory, go to Metrics > Import new metrics datasource > CSV.
  3. Upload the file, choose the orientation, and map columns.
  4. Define the metric names, aggregation, and gap-filling rules.

Google Sheet

  1. Share the sheet with importer-sheets@costory.io.
  2. Ensure the first row contains headers (date + metric columns).
  3. In Costory, go to Metrics > Import new metrics datasource > Google Sheet.
  4. Provide the Google Sheet ID and map the columns.

Datadog

  1. Create a Datadog integration in Integrations (API key, application key, region).
  2. In Costory, go to Metrics > Import new metrics datasource > Datadog.
  3. Select the Datadog configuration.
  4. Provide a metric query with a rollup (example):
    • avg:system.cpu.user{*} by {host}.rollup(avg, daily, 'UTC')
  5. Validate and finalize the metrics definition.
Datadog query reference: https://docs.datadoghq.com/api/latest/metrics/#query-timeseries-points

Datadog CI Visibility

  1. Create a Datadog integration in Integrations with CI Visibility access.
  2. In Costory, go to Metrics > Import new metrics datasource > Datadog CI Visibility.
  3. Provide the CI Visibility query, aggregation, and optional group-by fields.
API reference: https://docs.datadoghq.com/api/latest/ci-visibility-pipelines/#aggregate-pipelines-events

BigQuery

  1. Share your dataset with the Costory service account:
    • costory-<org-slug>@costory-production.iam.gserviceaccount.com
  2. In Costory, go to Metrics > Import new metrics datasource > BigQuery.
  3. Provide the BigQuery table path and map the columns (flat or columnar format).

GCS Inventory (Parquet)

  1. Share your GCS inventory bucket with the Costory service account:
    • costory-<org-slug>@costory-production.iam.gserviceaccount.com
  2. In Costory, go to Metrics > Import new metrics datasource > GCS Inventory.
  3. Provide the inventory file path (e.g., gs://bucket/path/to/data), bucket name, and search pattern.
  4. Validate and finalize the metrics definition.

Amplitude

  1. Get your Amplitude API key and secret key (Project settings).
  2. In Costory, go to Metrics > Import new metrics datasource > Amplitude.
  3. Provide the API key, secret key, and region.
  4. Costory syncs the last 12 months of data automatically.
See Correlate Cloud Costs with Active Users for a step-by-step guide on building a cost-per-user dashboard with Amplitude data.Amplitude API docs: https://amplitude.com/docs/apis/analytics/dashboard-rest

Parquet file (AWS S3)

  1. Store your metrics parquet files in S3.
  2. Create an IAM role with read-only S3 access and a web identity trust for Costory.
  3. In Costory, go to Metrics > Import new metrics datasource > Parquet file (AWS S3).
  4. Provide the bucket name, prefix, role ARN, and configure metric definitions (value column, date column, aggregation, gap-filling, dimensions, unit).

Next Steps

Last modified on March 9, 2026