- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
Datadog generates an additional metric for each resource monitored with the Azure integration: azure.*.count
. For example, Azure Virtual Machines monitored by Datadog reports azure.vm.count
.
The azure.*.count
metric is an improvement over azure.*.status
, which is deprecated.
The azure.*.count
metric provides two fundamental pieces of information:
The azure.*.count
metric is created in the same namespace as the other metrics for that resource type, for example: azure.network_loadbalancers.count
. It includes all of the same metadata tags as the other metrics in that namespace, plus as additional tag for status
.
Use the azure.*.count
metric to:
azure.vm.count
over everything and summing by status
.Note: In some cases, the default visualization settings can make it appear as though resources are being double counted intermittently in charts or query widgets. This does not affect monitors or widgets scoped to a specific status.
You can reduce this effect by turning off interpolation in charts or query widgets by setting Interpolation > none or using .fill(null)
.
For most resource types, the possible statuses are:
Virtual machines have more detailed statuses, including:
If you see a status of query_failed
you need to enable the Resource Health provider in Azure.
If your Azure integration is reporting metrics but not azure.*.count
, or azure.*.count
is returning status:query_failed
, your Azure subscription needs to register the Azure Resource Health provider.
Using the Azure Command Line Interface:
azure login # Login to the Azure user associated with your Datadog account
azure config mode arm
azure provider register Microsoft.ResourceHealth
The azure.*.count
metric should show in Datadog within 5 - 10 minutes.