- 필수 기능
- 시작하기
- 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+=`Status Pages are part of Datadog’s Incident Response suite, alongside On-Call and Incident Management. They let your team proactively communicate real-time service availability, incidents, and maintenance updates with customers or internal stakeholders through a shareable web page.
Use Status Pages to:
There are three RBAC permissions that are relevant to Status Pages. Users with the Datadog Admin Role have all the necessary permissions.
To create, update, or publish Status Pages, you must have status_pages_settings_read
, status_pages_settings_write
, and status_pages_incident_write
RBAC permissions. For more information, see Access Control.
Name | Description | Default Role |
---|---|---|
Status Pages Settings Read (status_pages_settings_read ) | View the list of Status Pages, the settings of each Status Pages, their Incidents, and launched Private Status Pages. | Datadog Read Only Role |
Status Pages Settings Write (status_pages_settings_write ) | Create and launch new Status Pages, and configure Status Pages settings. | Datadog Admin Role |
Status Pages Incident Write (status_pages_incident_write ) | Publish and update Incidents. | Datadog Admin Role |
Field | Description |
---|---|
Visibility | Choose who can access the page: - Public - Anyone with the link can view - Private - Only authenticated users within your Datadog organization can view |
Page name | Displayed as the page header (if no logo is uploaded). Example: Acme Cloud Platform |
Domain Prefix | Used as your status page subdomain prefix. Example: shopist → shopist.status.datadoghq.com - Must be globally unique - Lowercase, alphanumeric, and hyphenated - May affect links if changed later |
Company logo or Favicon (optional) | Upload a logo or favicon to personalize the appearance of your status page |
Components are the building blocks of your status page. Each one represents a service or feature your users care about. Some examples of components include:
You can add components to your status page either on intial setup or through the status page settings:
After you save your status page settings, click Launch Status Page to make the page available at its URL.
If you selected:
When an issue arises, you can communicate it clearly through your status page.
Field | Description |
---|---|
Title | Short, clear description of the incident Example: Increased error rates on US region |
Status | Current state of the incident: - Investigating - Identified - Monitoring - Resolved |
Message (optional) | Additional details for your users Examples: known cause, expected resolution time |
Affected Components | One or more components impacted by the incident |
Impact | Level of impact per component: - Operational - Degraded Performance - Partial Outage - Major Outage |
After an incident is published, the incident:
You can post updates over time to keep users informed, and then mark the incident as Resolved.
To match your branding, you have the option to map your status page to a custom domain like status.acme.com
.
Notes: