The Finout-Datadog integration offers multiple levels, granting users the flexibility to choose from diverse Finout features and supported Datadog products available at each level. Each level requires different Datadog scopes. To gain all Datadog capabilities and features in Finout, ‘not scoped’ key is required.
Datadog scopes | Finout platform functionality | Organization keys level | API Used |
usage_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 |
|
usage_read, metrics_read, timeseries_query | Parent organization + all multiple child-organizations |
| |
monitors_read, dashboards_read | CostGuard- Out-of-the-box actionable cost optimizations for Idle Synthetics. | Parent organization + all multiple child-organizations |
|
Not scoped |
| Parent organization + all multiple child-organizations |
|
Below is a detailed breakdown of each level, including the supported Datadog products and the required scopes.
Basic Datadog Integration
Finout’s most basic offering. Add your Datadog’s product cost to Finout’s MegaBill with breakdowns by, sub-products, regions, and organizations.
Finout supports all Datadog products.
Required scopes- usage_read
Note: For the basic Datadog integration, having keys for the parent organization is mandatory. However, for enhanced integrations, API keys for all multiple child organizations are required.
Enhanced Datadog Integration- Cost Per Tag Visibility
With this advanced integration level, you can add cost-per-tag visibility to the Finout MegaBill. By incorporating product tags, you can access a more comprehensive breakdown of your Datadog Logs and Timeseries products, facilitating precise cost attribution to these services.
Two groups of tags can be added to Finout:
Default Datadog set of tags per product
For example, the tags for Indexed Log- "service", "status", "datadog_index"
Required scopes- metrics_read, timeseries_query
Custom tags set by the customer
Customers have the freedom to set their own custom tags. Our process is designed to dynamically resolve tag values based on customer specifications. In cases where resolution is unsuccessful, Finout utilizes its default tag set as a fallback option.
Required scopes- not scoped
Please note: For Timeseries product, only the metric_name tag is available.
Enhanced Datadog Integration - CostGuard
Finout enables you to effortlessly access out-of-the-box actionable cost optimizations and insights for your Datadog usage via the CostGuard product.
Required scopes: monitor_read, dashboard_read
Enhanced Datadog Integration- Kubernetes Cost and Unit Metrics
Required scopes: not scoped