 |
VOOZH | about |
|
VOOZH | about |
When you configure a service account for a Datadog integration, you can incorporate metadata from your integrations into Catalog entity definitions. From there, you can use the Action Catalog to query external systems or trigger actions—such as creating incidents or updating tickets—without leaving Datadog.
| Integration | Description | Example actions (Action Catalog) |
|---|---|---|
| PagerDuty | Add PagerDuty metadata to a service so that the Catalog displays and links to information such as who is on-call and whether there are active PagerDuty incidents for the service. | Get current on-call, Trigger incidentSee all available actions. |
| Opsgenie | Add Opsgenie metadata to a service so that the Catalog displays and links to information such as who is on-call for the service. | Acknowledge alert, Get current on callSee all available actions. |
| StatusPage | Create, update, and retrieve details about incidents and components. | Create an incident, Update component statusSee all available actions. |
| Freshservice | Create, update, and query Freshservice tickets. | List tickets, Update ticketSee all available actions. |
| Slack | Send incident alerts or updates to Slack channels, and perform channel management. | Invite users to channel, Set channel topicSee all available actions. |
| Microsoft Teams | Send messages or prompts to Teams channels for incident collaboration. | Make a decision, Send a messageSee all available actions. |
| Jira | create and update issues directly from Datadog. | Create issue, Add commentSee all available actions. |
| Asana | Create and update Asana tasks, assign users, and apply tags. | Add tag to task, Update task completed statusSee all available actions. |
| LaunchDarkly | Track feature flag changes, let developers make changes without leaving the platform, and drive automation based on changes | Add expire user target date, Toggle feature flagSee all available actions. |
| Integration | Description | Example actions (Action Catalog) |
|---|---|---|
| GitHub | Create issues or PRs, manage repo files, and automate team access. | Add labels to pull request, Get team membershipSee all available actions. |
| GitLab | Manage issues, merge requests, branches, and commits. | Approve merge request, Cherry pick commitSee all available actions. |
| Other (Bitbucket, Azure Repos) | Interact with platforms not natively supported in Datadog Catalog or Action Catalog. | N/A; use HTTP actions and reqeusts to call platform APIs |
You can also use GitHub to manage entity definitions and configure the GitHub integration to automatically pull definitions into Catalog. Learn more about creating entity definitions and importing them from GitHub.
| Integration | Description | Example actions (Action Catalog) |
|---|---|---|
| GitHub Actions | View, launch, and coordinate CI/CD workflows on GitHub. | Get latest workflow run, Trigger github actions workflow runSee all available actions. |
| GitLab Pipelines | Manage GitLab project pipelines, cancel or retry jobs, and query pipeline results. | Get latest pipeline, Retry jobs in a pipelineSee all available actions. |
| Jenkins | Trigger and manage Jenkins jobs. | Submit Jenkins job, Get Jenkins job statusSee all available actions. |
| CircleCI | Interact with your CI pipelines. | Approve workflow job, Get job detailsSee all available actions. |
| Azure DevOps Pipelines (ADO) | Trigger pipelines and fetch run data—ideal for launching deployments or QA workflows based on monitor activity. | Get pipeline, Run pipelineSee all available actions. |
You can import entities from ServiceNow and Backstage into Datadog’s Catalog. Refer to the following documentation for details:
Datadog’s Infrastructure integrations and Resource Catalog provides a comprehensive inventory of integrations across AWS, Azure, and GCP. You can also leverage Datadog’s 1000+ actions in the Action Catalog to create custom visualizations, actions, and automations.
Additional helpful documentation, links, and articles:
| |
