Faster time to market
Ship customer-facing integrations without building custom pipelines.
DataDog Connector
Embed DataDog monitoring and observability in your app. Build customer-facing integrations that surface metrics, send events, forward alerts and automate incident workflows for your users using Cyclr’s low-code orchestration.
Reusable workflows
Author once, reuse across customers and tenants.
Governed MCP tools
Expose controlled DataDog actions as approved MCP tools.
Embedded experience
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
Overview
Datadog provides monitoring, metrics, logs and alerting for cloud-scale applications. Using Cyclr you can embed DataDog-driven experiences — surface dashboards and metrics, route alerts to downstream systems, automate incident playbooks and publish governed MCP tools for end users inside your SaaS product.
PRODUCT USE CASES
Top use cases
Quickly create in-app workflows that forward Datadog alerts, surface dashboard widgets, sync incidents to ticketing systems and automate metric-driven actions. Publish these integrations to customers through Cyclr’s embedded marketplace or expose them as governed MCP tools.
Automated incident creation
When DataDog monitor triggers, create tickets in your support system and start automated runbooks.
Embedded dashboards and metrics
Surface customer-specific DataDog metrics and dashboard widgets directly inside your app UI.
Alert forwarding and enrichment
Forward alerts to Slack, PagerDuty or third-party CRMs and enrich with tenant metadata.
ORCHESTRATION
How DataDog works with Cyclr
Cyclr sits between your SaaS product and DataDog to handle authentication, govern access and orchestrate every API call per customer, at scale.
- 1
Your SaaS product
Your app requests an action for a specific customer.
- 2
Cyclr orchestration
Cyclr authenticates, applies policies and routes the request.
- 3
DataDog
DataDog processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Available connector capabilities
Explore DataDog methods you can orchestrate through Cyclr.
Users2
List Updated Users
ActionGet the list of all updated users in the organization since last run. This list includes all users even if they are deactivated or unverified.
List Users
ActionGet the list of all users in the organization. This list includes all users even if they are deactivated or unverified.
Logs1
Upload Logs
ActionUpload logs to your DataDog platform.
Usage Metering2
List Historical Cost
ActionGet historical cost across multi-org and single root-org accounts.
List Estimated Cost
ActionGet estimated cost across multi-org and single root-org accounts.
Dashboards3
List Dashboards
ActionList all dashboards.
Get Dashboard
ActionGet a dashboard using the specified ID.
List Updated Dashboards
ActionList all updated dashboards since last run.
Organization2
List Managed Organizations
ActionList your managed organizations.
Get Organization Information
ActionGet organization information.
Metrics2
List Metrics
ActionList all metrics in DataDog.
Post Metrics
ActionPost metric data points to DataDog.
Roles2
List Roles
ActionReturns all roles, including their names and IDs.
List Updated Roles
ActionReturns all roles, including their names and IDs since last run.
TECHNICAL DETAILS
DataDog integration and API details
Review the sourced authentication and API behaviour used when configuring customer-facing DataDog integrations in Cyclr.
API and authentication
- API host
https://api.datadoghq.com- Authentication
- API key and application key (Datadog API keys / application keys)
- Credentials
api_key, application_key, optional site (api.datadoghq.com or api.datadoghq.eu)
- Method categories
Metrics, events, monitors, dashboards, hosts, logs, webhook integrations, integrations management
Pagination and rate limits
Pagination
Pagination varies by endpoint. Some use page[size] and page[cursor] with meta.pagination.next_cursor; others use start/count or offset parameters.
Rate limits
Rate limits vary by endpoint and resource. Exceeding limits returns 429 and X-RateLimit-* headers; contact Datadog to request increases.
IMPLEMENTATION
Authentication at a glance
Datadog uses organization API keys and user-scoped application keys. Write operations require an API key; API reads often require an application key. Keys are long lived and managed in the org settings.
- Authentication method
- API key and application key (Datadog API keys / application keys)
- Credential required
api_key, application_key, optional site (api.datadoghq.com or api.datadoghq.eu)
Before you begin:
View setup guideNew API or application keys may take a few seconds to propagate; implement retry/backoff.
COMMON QUESTIONS
Frequently asked questions
The connector needs an organization API key and an application key. Optionally set the Datadog site (US or EU) for the API host.
Yes. Datadog supports webhook integrations and the connector can create and manage webhook endpoints to forward monitor alerts.
Pagination is endpoint specific. Some APIs use page[size] and page[cursor] with meta.pagination.next_cursor; others use start/count or offsets.
Datadog enforces variable rate limits per endpoint. Exceeding limits returns 429 and X-RateLimit headers; implement retries and respect headers.
KEEP EXPLORING
Related resources and connectors
Documentation
What is iPaaS?
Read more →ProductHow to develop an API – Best Practices to Follow from Cyclr Developers
Read more →ProductMCP PaaS
Read more →Related connectorAmazon S3
Related Analytics connector for customer-facing integration workflows.
Related connectorKeen IO
Related Analytics connector for customer-facing integration workflows.
Related connectorElasticSearch
Related Data Tools connector for customer-facing integration workflows.