Documentdb Monitoring
Monitoring and diagnostics best practices for Azure DocumentDB — enabling diagnostic settings and slow-query logs, analyzing them in Log Analytics, and alerting on CPU / memory / IOPS / storage / connection saturation per cluster tier. Use when setting up observability on a new cluster, investigating production incidents, or tuning alert thresholds.
Install
$ agentstack add skill-azure-documentdb-agent-kit-monitoring ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Monitoring & Diagnostics — Azure DocumentDB
Rules
- [monitoring-slow-query-log](monitoring-slow-query-log.md) — Enable diagnostic settings and analyze slow-query logs in Log Analytics.
- [monitoring-metrics-alerts](monitoring-metrics-alerts.md) — Alert on CPU, memory, IOPS, storage, and connection saturation per cluster tier.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Azure
- Source: Azure/documentdb-agent-kit
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.