Datadog

Pull estimated and projected costs across all Datadog products into Pump View, including APM, Logs, Infrastructure, RUM, Synthetics, and more. Track your observability spend alongside cloud costs in a single dashboard.

Setup time: ~3 minutes

Access level: Read-only


Prerequisites

  • An API Key. Found under Datadog → Organization Settings → API Keys.

  • An Application Key with billing_read scope. The Application Key owner must have an Admin or Billing Admin role in Datadog.

  • Your Datadog site region. One of: us1, us3, us5, eu1, or ap1. Defaults to us1 if you're not sure.

Note: Datadog requires two keys (an API Key and an Application Key). Both are needed for the integration to work.


Setup Instructions

1. Get Your API Key

  1. Log in to Datadog as an Admin or Billing Admin.

  2. Go to Organization Settings → API Keys.

  3. Create a new API key or copy an existing one.

2. Create an Application Key

  1. Go to Organization Settings → Application Keys.

  2. Click New Application Key.

  3. Ensure the key has the billing_read scope.

  4. Copy the Application Key.

Tip: If you don't see the option to set scopes, your Datadog role may not have sufficient permissions. You need Admin or Billing Admin.

3. Know Your Site Region

Your Datadog site region determines which API endpoint Pump connects to. If you're unsure, check the URL in your browser when logged into Datadog:

URL contains
Region

app.datadoghq.com

us1 (default)

us3.datadoghq.com

us3

us5.datadoghq.com

us5

app.datadoghq.eu

eu1

ap1.datadoghq.com

ap1

4. Connect in Pump

  1. In Pump, go to Settings → Integrations.

  2. Find Datadog and click Connect.

  3. Enter your API Key, Application Key, and select your site region.

  4. Click Connect.

5. Verify

Pump validates both keys and fetches your org name, then backfills up to 365 days of cost data. All Datadog product costs should appear alongside your cloud spend within a few minutes.


What Data Does Pump Pull?

Data
Description

APM

Application performance monitoring costs

Logs

Log ingestion, indexing, and retention costs

Infrastructure

Host-based infrastructure monitoring costs

RUM

Real User Monitoring session costs

Synthetics

Synthetic test execution costs

Other products

Any additional Datadog products on your account (CSPM, CI Visibility, etc.)

Frequently Asked Questions

What's the difference between an API Key and an Application Key?

In Datadog, API Keys authenticate your organization, while Application Keys are tied to a specific user and control what data that user can access. Pump needs both: the API Key to identify your org, and an Application Key with billing_read scope to access cost data.

I created an Application Key but it doesn't have a scope option.

Scoped Application Keys require a recent Datadog plan. If you don't see scope options, check with your Datadog account rep. Also confirm you have Admin or Billing Admin role, as lower roles may not be able to set billing scopes.

How do I find my site region?

Look at the URL when you're logged into Datadog. The default region is us1 (app.datadoghq.com). See the region table above for the full mapping.

How far back does Pump pull data?

Pump backfills up to 365 days of historical cost data from the date you connect.

Does Pump see my logs, traces, or application data?

No. Pump only accesses billing and cost data via the billing_read scope. It cannot see your logs, APM traces, dashboards, or any application-level data.

Can I revoke the keys later?

Yes. You can delete either key from Datadog under Organization Settings → API Keys or Application Keys at any time. Deleting either key will disconnect the integration.

My data isn't showing up after connecting.

  • Confirm you provided both an API Key and an Application Key (they are different).

  • Verify the Application Key has the billing_read scope.

  • Check that you selected the correct site region.

  • Ensure the Application Key owner has Admin or Billing Admin role.

  • Wait a few minutes for the initial backfill.

  • If the issue persists, reach out to [email protected]envelope.

Last updated

Was this helpful?