Service Mappings

After connecting a provider, you need to map it to the BlameTrail services it monitors. Mappings tell BlameTrail which provider to query when fetching metrics or logs for a specific service.

Creating a mapping

1. In the provider connection detail panel, click Add Service Mapping.
2. Select a service from the dropdown.
3. Optionally configure:
   • Metrics filters — Key-value pairs appended to every metrics query (e.g., service=api, env=production)
   • Log filters — Key-value pairs appended to every log query
   • Default metrics query — A PromQL or Datadog query to use as the default for this service
   • Default logs query — A LogQL or CloudWatch Insights query to use as the default
4. Click Save.

Multiple providers per service

A single service can be mapped to multiple providers. For example, you might map a service to both Prometheus (for metrics) and Loki (for logs). BlameTrail queries all mapped providers in parallel and merges the results.

Environment overrides

Mappings support environment-specific overrides. If your staging and production instances use different labels or log groups, you can configure per-environment filters:

{
  "metrics_filters": { "env": "production" },
  "environment_overrides": {
    "staging": {
      "metrics_filters": { "env": "staging" }
    }
  }
}

Enabling and disabling

Mappings can be toggled on or off without deleting them. A disabled mapping is skipped during queries. This is useful for temporarily silencing a noisy provider without losing configuration.

Preview

After creating a mapping, you can click Preview to test the query and see sample results before relying on it during incidents.