- 필수 기능
- 시작하기
- 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+=`This guide provides steps for creating a monitor template and best practices to follow during the creation process.
Datadog Monitors track key metrics, so you can efficiently monitor your infrastructure and integrations. Datadog provides a set of out-of-the-box monitors for many features and integrations. View these monitors in your Monitors Template list.
Create an out-of-the-box monitor to help users find value in your Datadog integration. To create a Datadog integration, see Create a New Integration.
In your Datadog sandbox, create a monitor.
Follow the best practices listed in this guide to configure your monitor.
Within your integration in the Integration Developer Platform, navigate to the Content tab. From there, select import monitor to choose from a list of available monitors. You can select up to 10 monitors to include with your integration.
To see the out-of-the-box monitor:
Find your monitor in the Monitors Template list. Ensure logos render correctly on the Monitors Template lists page.
In addition to the monitor definition, the Title, Description, and Tags fields are required for monitor templates. Set tags to “integration:<app_id>”, see other available monitor tags here. For more information, see the documentation on configuring a monitor.
The title allows users to quickly understand the underlying failure mode the alert is covering.
Needs revision | Better | Best |
---|---|---|
High Unacknowledged Messages reported on {{host.name}} | High Unacknowledged Messages reported | Unacknowledged Messages are higher than usual |
Provides extra context around the failure mode and also about the impact this mode can have on the system. It should allow users to understand at a glance whether it is relevant or not for them to create a monitor out of it.
Needs revision | Better | Best |
---|---|---|
Notify your team when unacked message are high. | Unacked messages are those that have been delivered to a consumer but have not been acknowledged as processed or handled. This monitor tracks the ratio of unacked messages. | Unacked messages are those that have been delivered to a consumer but have not been acknowledged as processed or handled. This monitor tracks the ratio of unacked messages to avoid potential bottlenecks which could lead to delays in message processing. |
추가 유용한 문서, 링크 및 기사: