- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
",t};e.buildCustomizationMenuUi=t;function n(e){let t='
",t}function s(e){let n=e.filter.currentValue||e.filter.defaultValue,t='${e.filter.label}
`,e.filter.options.forEach(s=>{let o=s.id===n;t+=``}),t+="${e.filter.label}
`,t+=`To add entity definitions to Software Catalog, you can:
To create entity definitions in the Datadog UI:
Navigate to the Software Catalog Setup & Config page.
Click Create a New Entry.
Specify your service details, including metadata such as ownership and documentation links.
(Optional) Switch to YAML or JSON to see the generated code and cURL command. In the code editors, Datadog automatically flags invalid data.
Submit the metadata by clicking Save Entry or by running the provided cURL command.
Note: You must have Software Catalog Write permission to save the entry.
To automate import through GitHub, Terraform, the Datadog Software Metadata Provider, or the Datadog Service Definition API:
Create service.datadog.yaml
or entity.datadog.yaml
to define your entity (Datadog accepts both file names).
Name your entity in the dd-service
(schema version v2.2 or prior) or name
(schema version v3.0+) field.
For example:
service.datadog.yaml
schema-version: v2.2
dd-service: my-unmonitored-cron-job
team: e-commerce
lifecycle: production
application: shopping-app
description: important cron job for shopist backend
tier: "2"
type: web
contacts:
- type: slack
contact: https://datadogincidents.slack.com/archives/XXXXX
links:
- name: Common Operations
type: runbook
url: https://datadoghq.atlassian.net/wiki/
- name: Disabling Deployments
type: runbook
url: https://datadoghq.atlassian.net/wiki/
tags: []
integrations:
pagerduty:
service-url: https://datadog.pagerduty.com/service-directory/XXXXXXX
External Resources (Optional)
(Optional) Register multiple services in one YAML file by separating each definition with three dashes (---
).
Import the definition in one of the following ways:
Terraform: Create and import the definition as a Terraform resource.
Note: Creating and managing services in the Software Catalog through automated pipelines requires Datadog Provider v3.16.0 or later.
Datadog APIs: Import your definition using the Service Definition API (for schema v2.x) or the Software Catalog API (for schema v3+), which are both open-sourced GitHub Action solutions.
GitHub: Configure the Datadog GitHub integration to manage and import your definitions.
Configure the GitHub integration to directly link from where you view the service’s definition in the Software Catalog to where it’s stored and editable in GitHub. Datadog scans for the service.datadog.yaml
and entity.datadog.yaml
files throughout each repository with read permissions.
To install the GitHub integration:
When the GitHub integration is set up for your definitions, an Edit in GitHub button appears in the service’s Definition tab and links you to GitHub to commit changes.
After you update the YAML files for your repositories, your changes propagate to the Software Catalog. You can register multiple services in one YAML file by creating multiple YAML documents. Separate each document with three dashes (---
).
To prevent accidental overwriting, create and modify your definition files with either the GitHub integration or the Definition API endpoints. Updating the same service using both the GitHub and the API may result in unintended overwriting.
To validate your service definitions ingested by Datadog’s GitHub integration, you can view events when services are updated or when there is an error. To view validation errors in Event Management, filter by source:software_catalog
and status:error
. Adjust the timeframe as needed.