For AI agents: A markdown version of this page is available at https://docs.datadoghq.com/internal_developer_portal/homepage.md. A documentation index is available at /llms.txt.
This product is not supported for your selected Datadog site. ().
IDP Homepage showing a personalized view of GitHub pull requests awaiting review and Jira tickets

Overview

The IDP Homepage provides a centralized view of your team’s entities and your daily tasks.

With this view, you can:

  • View key information about your team’s entities, including scorecards, recent deployments, monitors, issues, incidents, dashboards, and on-call status.
  • Track tasks assigned to you across GitHub and Jira.
  • Identify alerting monitors or failed deployments.

Prerequisites

The Homepage aggregates data from your Datadog integrations. To populate the task sections, configure the following integrations and webhooks before using the Homepage:

  • GitHub: Install and configure the GitHub integration, and set up a GitHub webhook so that repository events (such as pull request activity) reach Datadog in real time. The GitHub PRs section requires this webhook to display current pull request data. For setup steps, see GitHub.
  • Jira: Configure the Jira integration, and set up a Jira webhook so that issue events reach Datadog. The Jira tab in the Your Tickets section requires this webhook to display your assigned issues. For setup steps, see Configure a Jira webhook.

GitHub PRs

PRs assigned to the user

The GitHub PRs section consolidates your personal action items from GitHub, displaying PRs in the following states:

  • Needs your review
  • Returned to you
  • Approved
  • Waiting for reviewers
  • Recently merged

Each PR includes:

  • Repository and PR number
  • Title
  • Status (Open / Draft / Merged)
  • Assignee / Reviewer

If your organization has not configured the GitHub integration, this section displays an empty state with a prompt to enable it from the GitHub integration tile. To read PRs from GitHub, this integration requires the following permissions:

  • Members: Read
  • Metadata: Read
  • Pull Requests: Read
  • Contents: Read
  • Statuses: Read
  • Checks: Read

In addition to these permissions, the GitHub PRs section requires a configured GitHub webhook so that pull request events reach Datadog in real time. For setup steps, see GitHub.

If you have multiple GitHub orgs connected within Datadog, users must have the Datadog Integrations Read Permissions to toggle between orgs.

Your tickets

Your Tickets section showing Jira and Cases tabs with items assigned to the user

The Your Tickets section consolidates the items assigned to you across Jira and Datadog Case Management, so you can track your open work without leaving the Homepage. Switch between the Jira and Cases tabs to view each source, and use Display to change how items are shown.

Jira

The Jira tab lists the Jira tickets assigned to you, grouped by status category: To Do, In Progress, and Done. Each ticket includes:

  • Key
  • Title (with a comment count when comments exist)
  • Status
  • Created
  • Updated
  • Priority
  • Due
  • Assignee

Cases

The Cases tab lists the Datadog Case Management cases assigned to you, grouped by status: Open, In Progress, and Closed. Each group shows a count.

Each case includes:

  • Case key
  • Title (with a comment count when comments exist)
  • Status
  • Updated
  • Priority
  • Due date
  • Assignee

Cases appear automatically when they are assigned to you. For more information, see Case Management.

Services and entities

Services & entities for the user

The Services & Entities section displays your team’s key services and entities, aggregated automatically from linked Datadog products and integrations. You can filter by recently viewed entities, entities owned by your team, or entities you’ve favorited.

Each entity includes the following information:

FieldDescription
TypeThe entity type (for example, Service, Monitor, or Incident).
NameThe entity’s display name or identifier.
ScorecardsA summary of the entity’s health based on reliability, performance, and error budgets.
Last DeployThe most recent deployment detected by APM or CI integrations.
MonitorsThe number and status of monitors associated with the entity.
IssuesActive issues related to the entity, aggregated from linked tracking tools.
IncidentsOpen incidents associated with the team’s entities.
DashboardsKey dashboards linked to the entity.
On-CallThe current on-call responder for the team or entity.

Extend the Homepage with custom apps

In addition to the built-in sections, the Apps section lets you add custom apps to the Homepage, so you can bring together the data and actions you find most useful, whether they come from Datadog, an internal tool, or a third-party service. Datadog provides two ways to build these apps:

  • App Builder: A low-code, drag-and-drop builder for internal tools. Apps combine prebuilt UI components, Datadog data sources (such as metrics, logs, and monitors), and out-of-the-box actions for services such as GitHub and AWS. For more information, see App Builder.
  • Datadog Apps: A code-based path for apps you build locally with React and TypeScript (or JavaScript), using a CLI and your standard development workflow. Choose Datadog Apps when you need team collaboration with source control and CI/CD, AI-assisted local development, integration with services beyond the Action Catalog, or full control over the app’s UI and logic. For more information, see Datadog Apps.

To make a custom app available here, first publish it and define its permissions so that your team can view and use it.

To add an app to the Homepage:

  1. In the Apps section, click Add App.
  2. Choose a blueprint to start from a prebuilt app, or choose a custom app that your organization has already built.
  3. Configure the app, then add it to the Homepage.

Further reading

Additional helpful documentation, links, and articles: