Datadog Integration Levels

Finout connects to Datadog using API and Application keys generated in your Datadog account.

During setup, Datadog will require you to select the permission scopes granted to the Application key. These scopes determine what data Finout can access and, therefore, which Finout features can be enabled.

Because of this, the Datadog integration is structured in multiple integration levels. Each level requires a different set of scopes and unlocks different functionality inside Finout.

As broader scopes are granted, Finout gains access to additional Datadog data, enabling more advanced features.

Integration Levels Overview

The following table summarizes the Finout functionality available at each integration level and the required Datadog scopes.

Datadog scopes	Finout platform functionality	Organization keys level	API Used
usage_read, billing_read	Basic Datadog cost center integration - View Datadog’s products in Finout’s MegaBill with breakdowns by usage type (committed / on-demand cost), products, and organization.	Only Parent organization	get-hourly-usage-by-product-family Get estimated cost
usage_read, metrics_read, timeseries_query logs_read_config billing_read	Enhanced Datadog integration- Default Datadog list of tags per product	Parent organization + all multiple child-organizations	query-timeseries-points list-tags-by-metric-name
monitors_read, dashboards_read	CostGuard- Out-of-the-box actionable cost optimizations for Idle Synthetics. Note: Currently, the default integration is Usage Attribution Tags for new Datadog cost centers created since April 2025. For cot centers created before that, the default integration remains Custom Tags, and they should contact Finout support at [email protected] to transition to UAT-based integration.	Parent organization + all multiple child-organizations	get-all-dashboards get-a-dashboard get-all-monitor-details
logs_read_config, metrics_read, hosts_read, timeseries_query	Enhanced Datadog integration- Kubernetes cost and unit metrics	Parent organization + all multiple child-organizations	Logs Indexes Metrics Hosts Metrics
Not scoped	Enhanced Datadog integration- custom tags set by the customer Products basic list of tags- Indexed Log	Parent organization + all multiple child-organizations	get-all-indexes list-tags-by-metric-name get-all-hosts-for-your-organization query-timeseries-points

To learn more about each capability and the data it requires, see the detailed explanations below.

Basic Datadog Integration

The Basic Datadog integration enables Datadog cost visibility in Finout.

With this integration:

• Datadog is added as a cost center in Finout

• Datadog costs appear in the MegaBill

• Costs can be analyzed by:

• Datadog product

• usage type (committed vs on-demand)

• Organization

• Usage Attribution Tags

Finout retrieves this information using Datadog billing APIs, allowing organizations to monitor their Datadog spend directly within Finout.

Required scopes: usage_read, billing_read

Enhanced Datadog Integration

The Enhanced Datadog integration expands the basic integration by enabling deeper cost analysis using Datadog tags and metric metadata.

This allows Finout to:

• Break down Datadog costs using the default Datadog custom tags

• Provide richer cost attribution across Datadog services

• support analysis across parent and child Datadog organizations

These capabilities rely on additional Datadog APIs that provide access to metrics and metadata.

Required scopes: usage_read, metrics_read, timeseries_query, logs_read_config, billing_read

Kubernetes Metrics Integration

Datadog can also be used as a Kubernetes metrics source in Finout.

When enabled, Finout retrieves Kubernetes resource usage metrics from Datadog to calculate how to distribute cluster infrastructure costs across Kubernetes workloads.

This enables Finout to:

• Allocate Kubernetes cluster costs across namespaces, workloads, and pods

• Combine Kubernetes usage metrics with cloud infrastructure billing data

• Provide Kubernetes cost visibility across Finout dashboards and analysis tools

This integration relies on Datadog timeseries metrics APIs to retrieve CPU and memory usage metrics.

Required scopes: logs_read_config, metrics_read, hosts_read, timeseries_query

CostGuard Integration

The CostGuard integration enables Finout’s Datadog optimization insights.

With this level enabled, Finout can analyze Datadog configuration data to generate cost-optimization recommendations.

This includes:

• Identifying Idle Synthetics

• Surfacing optimization opportunities within CostGuard

• Providing actionable insights to reduce unnecessary Datadog spend

To enable this functionality, Finout requires read access to Datadog monitors and dashboards.

Required scopes: monitors_read, dashboards_read