Skip to main content

Connecting a Datadog Service to Uniskai

Uniskai can collect and display cost and usage data from Datadog alongside your cloud providers. Datadog is added under Third-party connections in Account manager, and once connected its costs appear in the same Cloudcosts modules as AWS, Azure, GCP, and OCI data.

To connect Datadog, you first create both keys in Datadog, then add the account in Uniskai.

How it works

Object

Where it is created

Purpose

Datadog API key

Datadog → Organization Settings → API Keys

Authenticates Uniskai to the Datadog organization.

Datadog Application key (with usage_read and billing_read scopes)

Datadog → Personal Settings → Application Keys

Grants read access to usage and billing data.

Datadog account

Uniskai → Account manager → Third-party connections

The connection record in Uniskai. Stores the account name, keys, and site.

Prerequisites

  • A Datadog account with permission to create API keys and Application keys.

  • The Datadog site your account is hosted on. It matches your Datadog URL (for example, app.datadoghq.eu → datadoghq.eu).

  • Cost data is only available for parent-level Datadog organizations. Check your Datadog Organization Settings if you are not sure.

How to connect Datadog:

1. Create an API key in Datadog

  • In Datadog, open Organization Settings → API Keys.

  • Select + New Key.

  • Enter a Name for the key and select Create Key.

  • Copy the key value.

The API key is a plain organization key — it has no scopes.

2. Create an Application key in Datadog

  • In Datadog, open Personal Settings → Application Keys.

  • Select + New Key.

  • Enter a Name and select Create Key.

  • Copy the key value and store it securely.

  • On the key, next to Scope, select Edit.

  • In Edit Key Scope, search for billing and check billing_read.

  • Search for usage, check usage_read, and select Save.

  • Back in the key dialog, select Finish.

The Application key value is shown only once, at creation. Copy it before closing the dialog.

3. Add the Datadog account in Uniskai

  • In Uniskai, open Account manager and select Add New Account.

  • Under Third-party connections, select the Datadog card.

  • In Account name, enter a name that identifies this connection, for example Datadog Production.

  • In API key, paste the API key created earlier.

  • In Application key, paste the Application key created earlier.

  • In Site, select the site that matches your Datadog URL (for example, datadoghq.eu).

  • Check This is a parent-level organization.

  • Select Connect account.

View Datadog costs

Costs for the current month appear in Costs analysis right after the account is connected. Historical data is collected separately and can take up to a day to show up in full.

  • In the left menu, open Cloudcosts → Costs analysis.

  • Set Time range to the period you want to review, for example Current month.

  • In Provider, select Datadog.

  • Clear any exclusion filters that would hide the data. Usage Account, Service Category, and Service Name may be set to is not with values pre-selected — remove those values.

  • Select Apply filters.
    If the data does not look up to date, select Refresh to reload it.

Create a chart of Datadog costs (optional)

You can build a custom chart to visualize Datadog spend:

  • Create a new chart on the billing.focus_distributed dataset.

  • Set the metric to SUM(BilledCost).

  • Add the filter ServiceProviderName IN ('Datadog').

  • To break the cost down by service, set the X-axis (dimension) to ServiceName.

The chart then shows Datadog billed cost and can be added to a dashboard.

Results

The connected account appears in Account manager under the Datadog tab, with

Access Read only, Connection Access key, and Status OK. Use Details to view

the connection, or the chart icon in Actions to open a cost chart.

Datadog data is available in Costs analysis:

  • Cost by Provider includes Datadog.

  • Top Services by Cost includes your Datadog services.

  • Daily Cost Trend shows Datadog spend over the selected period.

  • Provider is available as a filter value across Cloudcosts modules.

Key notes / limitations

  • The Application key needs both scopes. It must have usage_read and billing_read, or the connection will not read cost and usage.

  • The Site must match your Datadog URL. Selecting the wrong site prevents the connection from reaching your data.

  • Cost data requires a parent-level organization. Check This is a parent-level organization; if your organization is not parent-level, cost data is not available.

  • The connection is read-only and can be cancelled at any time.

Did this answer your question?