Getting Started with Internal Developer Portal

Docs > Getting Started > Getting Started with Internal Developer Portal

Overview

Datadog’s Internal Developer Portal (IDP) helps you unify software metadata, live telemetry, and developer workflows in a single platform. This guide walks you through setting up each core IDP component:

Catalog: Real-time inventory of entities and environments, enriched with ownership and operational metadata.
Scorecards: Measure adoption of engineering best practices using rules-based evaluations.
Self-Service Actions: Enable developers to execute standardized tasks with a single click.
Engineering Reports: Visualize quality, reliability, and compliance metrics across your stack.
Overview Pages: Give developers and teams a personalized view of their entities, issues, and action items.

Whether you’re starting from scratch or integrating with existing systems like Backstage or ServiceNow, use this guide to get started with IDP.

Prerequisites

If you have not already, create a Datadog account.

Step 1: Populate Catalog

IDP starts with Catalog, a real-time inventory of your software architecture’s key building blocks. In Datadog, these are called entities—they can represent individual services, APIs, or grouped Systems.

You can add entities from:

APM, USM, and RUM: Automatically discovered based on application telemetry
Manual definitions: Created through Datadog or imported through tools like Terraform, Datadog APIs, or the GitHub integration
Third-party systems: Through integrations with ServiceNow and Backstage

Start with a basic definition to register the entity, then enrich it with metadata to add ownership and operational context, including:

Ownership info and team contacts
Documentation, dashboards, runbooks
Deployment pipelines and config links
Production readiness data through unified service tagging

The following example defines a system entity representing an application composed of multiple services. It includes metadata such as display name, ownership, contacts, related documentation, integrations, and associated service components.

entity.datadog.yaml

apiVersion:v3kind:systemmetadata:name:myappdisplayName:My Apptags:- tag:valuelinks:- name:shopping-cart runbooktype:runbookurl:https://runbook/shopping-cart- name:shopping-cart architectureprovider:gdocurl:https://google.drive/shopping-cart-architecturetype:doc- name:shopping-cart Wikiprovider:wikiurl:https://wiki/shopping-carttype:doc- name:shopping-cart source codeprovider:githuburl:http://github/shopping-carttype:repocontacts:- name:Support Slacktype:slackcontact:https://www.slack.com/archives/shopping-cartowner:myteamadditionalOwners:- name:opsTeamtype:operatorintegrations:pagerduty:serviceURL:https://www.pagerduty.com/service-directory/Pshopping-cartspec:components:- service:myservice- service:otherservice

Read the Catalog setup guide to learn how to add or import entities, and review the entity model reference for schema details.

Step 2: Evaluate entity quality with Scorecards

Use Scorecards to assess whether entities meet your organization’s standards. Scorecards can measure:

Monitoring coverage
Production readiness
Security posture
Internal tooling adoption
Ownership and documentation

Datadog Scorecards include 10 out-of-the-box rules across observability practices, ownership tagging, and production readiness checkpoints. You can group rules into levels to categorize them by their criticality-level 1 (basic expectations), level 2 (recommended practices), and level 3 (advanced/aspirational goals).

In addition to using default rules, you can define custom rules to reflect your internal standards:

Go to the Scorecards page and click Create Rule.
Specify the rule name, the scorecard it belongs to, a description, and the owning team.
Send an outcome of pass, fail, or skip for each entity in one of the following ways:
- Manually through the Datadog UI
- Programmatically through the Scorecards API
- Automatically, using Workflow Automation to post outcomes on a schedule
View an overview of outcomes on the Scorecards page.

Learn more about scorecard configuration and custom rules in the Scorecards documentation.

Step 3: Use Self-Service Actions

Self-Service Actions let you run repeatable tasks through a UI or API. For example, use Self-Service Actions to:

Actions can be backed by automation systems like Terraform, GitHub Actions, or internal scripts. Self Service Actions offer over 1000+ pre-built integrations with tools across source code management (for example, GitHub and GitLab), ticketing and incident management (for example, Jira, ServiceNow, and PagerDuty), chat (for example, Slack and Microsoft Teams), cloud providers (for example, AWS, GCP, and Azure), and more. You can connect with any additional endpoints, including private resources, leveraging HTTP requests and private action runners.

Get started by exploring the Self-Service Actions Blueprint Library in Datadog for example apps that you can customize for your use case.

To start automating developer workflows, explore the Self-Service Actions documentation.

Step 4: Monitor engineering health with reports

Engineering Reports provide an at-a-glance view of:

Scorecards performance across all teams
Org-wide reliability trends based on SLOs and incident performance
Velocity and stability of software development

Explore Engineering Reports in the Datadog app. These reports are automatically generated and updated in real time.

Read the Engineering Reports documentation for more details on available reports and configuration options.

Step 5: Use overview pages for personalized insights

Overview pages surface high-level metrics and action items tailored to individual contributors and teams.

Start with the developer overview page, which shows:

Your open Jira tickets and GitHub PRs
Your team’s Monitors, Incidents, SLOs, and Scorecards
Active issues, errors, and Watchdog alerts

For setup and customization tips, read the Overview Pages documentation.

URL: https://docs.datadoghq.com/getting_started/internal_developer_portal/