Integrations

Docs > Internal Developer Portal > Integrations

Overview

When you configure a service account for a Datadog integration, you can incorporate metadata from your integrations into Software Catalog entity definitions. From there, you can use the Actions Catalog to query external systems or trigger actions—such as creating incidents or updating tickets—without leaving Datadog.

Request a new integration

Request Access

Collaboration, incident management, and ticketing

Integration	Description	Example actions (Action Catalog)
PagerDuty	Add PagerDuty metadata to a service so that the Software 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 incident` See all available actions.
OpsGenie	Add OpsGenie metadata to a service so that the Software Catalog displays and links to information such as who is on-call for the service.	`Acknowledge alert`, `Get current on call` See all available actions.
StatusPage	Create, update, and retrieve details about incidents and components.	`Create an incident`, `Update component status` See all available actions.
Freshservice	Create, update, and query Freshservice tickets.	`List tickets`, `Update ticket` See all available actions.
Slack	Send incident alerts or updates to Slack channels, and perform channel management.	`Invite users to channel`, `Set channel topic` See all available actions.
Microsoft Teams	Send messages or prompts to Teams channels for incident collaboration.	`Make a decision`, `Send a message` See all available actions.
Jira	create and update issues directly from Datadog.	`Create issue`, `Add comment` See all available actions.
Asana	Create and update Asana tasks, assign users, and apply tags.	`Add tag to task`, `Update task completed status` See 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 flag` See all available actions.

Setup examples

PagerDuty

You can connect any service in your PagerDuty Service Directory. You can map one PagerDuty service to each service in Software Catalog.

If you have not already done so, set up the Datadog PagerDuty integration.
Obtain your PagerDuty API Access Key.
Paste the key on the PagerDuty Integration Setup page.

Add PagerDuty information to the entity definition:

...
integrations:
  pagerduty: https://www.pagerduty.com/service-directory/shopping-cart
...

OpsGenie

To add OpsGenie metadata to an entity definition:

If you have not already done so, set up the Datadog OpsGenie integration.
Obtain your OpsGenie API Access Key and ensure it has configuration access and read permissions.
At the bottom of the integration tile, add an account, paste your OpsGenie API access key, and select the region for your OpsGenie account.

Update the entity definition with OpsGenie metadata. For example:

"integrations": {
  "opsgenie": {
        "service-url": "https://www.opsgenie.com/service/123e4567-x12y-1234-a456-123456789000",
        "region": "US"
  }
}

Once you’ve completed these steps, an On Call information box appears in the Ownership tab for services in Software Catalog.

On Call information box displaying information from OpsGenie in the Software Catalog

Source code management

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 membership` See all available actions.
GitLab	Manage issues, merge requests, branches, and commits.	`Approve merge request`, `Cherry pick commit` See all available actions.
Other (Bitbucket, Azure Repos)	Interact with platforms not natively supported in Datadog Software Catalog or Actions 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 Software Catalog. Learn more about creating entity definitions and importing them from GitHub.

CI/CD

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 run` See all available actions.
GitLab Pipelines	Manage GitLab project pipelines, cancel or retry jobs, and query pipeline results.	`Get latest pipeline`, `Retry jobs in a pipeline` See all available actions.
Jenkins	Trigger and manage Jenkins jobs.	`Submit Jenkins job`, `Get Jenkins job status` See all available actions.
CircleCI	Interact with your CI pipelines.	`Approve workflow job`, `Get job details` See 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 pipeline` See all available actions.

CMDBs and internal developer portals

You can import entities from ServiceNow and Backstage into Datadog’s Software Catalog. Refer to the following documentation for details:

Cloud Resources

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.