- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
This page explains how to resolve common issues with setting up and using Database Monitoring with MongoDB. Datadog recommends staying on the latest stable Agent version and adhering to the latest setup documentation, as it can change with Agent version releases.
MongoDB cluster_name
should follow Datadog tag naming conventions.
If your MongoDB cluster_name
contains uppercase characters or spaces, the Agent normalizes the cluster name to lowercase and replaces spaces with underscores. For example, if your cluster name is My Cluster
, the Agent normalizes it to my_cluster
.
To avoid inconsistencies and unexpected behavior, ensure that your cluster_name
follows Datadog tag naming conventions.
If you are using MongoDB Atlas, you might encounter a ServerSelectionTimeoutError
when connecting to the cluster. This error occurs when the Agent is unable to connect to the MongoDB Atlas cluster due to a network issue or TLS misconfiguration. To resolve this issue, ensure that tls
is set to true
in the integration configuration file. If you are still encountering issues, check the MongoDB Atlas cluster’s network access configuration to ensure that the Agent’s IP address is allowed to connect to the cluster.