AWS DocumentDB Integration
Monitor MongoDB-compatible cluster metrics, query performance, and replica lag across your DocumentDB clusters. Get AI-powered anomaly detection and failover correlation for your managed document database.
How It Works
Create IAM Role for Metric Streams
Provision an IAM role with CloudWatch permissions scoped to the AWS/DocDB namespace. TigerOps uses this role to deliver DocumentDB cluster and instance metrics via Firehose.
Deploy CloudWatch Metric Streams
Run the TigerOps CloudFormation stack to stream the AWS/DocDB namespace. Connection counts, query latency, and replica lag metrics begin flowing to TigerOps immediately.
Enable Slow Query Profiling
Set profiler_threshold_ms on your DocumentDB cluster to log slow queries to CloudWatch Logs. TigerOps ingests these logs and correlates slow query patterns with metric spikes.
Configure Replica Lag Alerts
Set replica lag SLOs per cluster. TigerOps fires predictive alerts when lag trends upward and identifies whether the primary or replica instance is the bottleneck.
What You Get Out of the Box
Cluster Health Monitoring
Primary and replica instance status, connection counts, database connections per instance, and failover event detection across your DocumentDB clusters.
Query Performance Metrics
Read and write latency, operations per second, and document scan rates per instance. Identify query patterns driving high read latency or excessive collection scans.
Replica Lag Monitoring
Per-replica replication lag in milliseconds with historical trending. TigerOps predicts lag breach thresholds and alerts before read replicas serve stale data.
CPU & Memory Utilization
CPU utilization, freeable memory, and swap usage per instance. Alert before resource saturation causes query performance degradation or connection drops.
Storage & I/O Metrics
Volume read and write IOPS, volume bytes read/written, and volume used storage. Prevent storage exhaustion and track I/O throughput trends per cluster.
AI Query Anomaly Detection
TigerOps establishes query rate baselines per collection and alerts on anomalous scan rates, correlating sudden query load increases with application deployments.
CloudFormation Stack for DocumentDB Metric Streams
Deploy the TigerOps CloudFormation stack to stream DocumentDB cluster metrics and enable slow query log ingestion.
# TigerOps CloudFormation — DocumentDB Metric Streams
# aws cloudformation deploy \
# --template-file tigerops-documentdb-streams.yaml \
# --stack-name tigerops-documentdb \
# --capabilities CAPABILITY_IAM
Parameters:
TigerOpsApiKey:
Type: String
NoEcho: true
ClusterIdentifier:
Type: String
Resources:
TigerOpsDocDBStream:
Type: AWS::CloudWatch::MetricStream
Properties:
Name: tigerops-docdb-stream
FirehoseArn: !GetAtt TigerOpsDeliveryStream.Arn
RoleArn: !GetAtt MetricStreamRole.Arn
OutputFormat: opentelemetry0.7
IncludeFilters:
- Namespace: AWS/DocDB
TigerOpsDeliveryStream:
Type: AWS::KinesisFirehose::DeliveryStream
Properties:
HttpEndpointDestinationConfiguration:
EndpointConfiguration:
Url: https://ingest.atatus.net/api/v1/cloudwatch
AccessKey: !Ref TigerOpsApiKey
RequestConfiguration:
CommonAttributes:
- AttributeName: cluster
AttributeValue: !Ref ClusterIdentifier
- AttributeName: service
AttributeValue: documentdb
RetryOptions:
DurationInSeconds: 60
# Enable slow query profiling on DocumentDB cluster:
# aws docdb modify-db-cluster-parameter-group \
# --db-cluster-parameter-group-name my-param-group \
# --parameters ParameterName=profiler,ParameterValue=enabled \
# --parameters ParameterName=profiler_threshold_ms,ParameterValue=100Common Questions
Which DocumentDB metrics does TigerOps collect?
TigerOps collects all AWS/DocDB CloudWatch metrics including DatabaseConnections, ReadLatency, WriteLatency, ReadThroughput, WriteThroughput, CPUUtilization, FreeableMemory, FreeLocalStorage, ReplicationLag, OpcountersInsert, OpcountersQuery, and NetworkThroughput per instance and cluster.
Does TigerOps support DocumentDB global clusters?
Yes. DocumentDB global cluster secondary regions publish metrics with the same AWS/DocDB namespace. TigerOps allows you to filter by region and compare primary versus global secondary cluster replica lag and query performance side by side.
Can TigerOps ingest DocumentDB slow query logs?
Yes. DocumentDB profiler logs delivered to CloudWatch Logs can be streamed to TigerOps via a subscription filter. Slow query patterns, collection names, query plans, and execution times are indexed and linked to metric spikes in the same timeline.
How does TigerOps handle DocumentDB failover events?
TigerOps captures DocumentDB cluster event messages from CloudWatch Events/EventBridge. When a failover occurs, it creates a timeline annotation, measures connection drop and recovery duration, and correlates the failover with application error rate changes.
Does TigerOps monitor DocumentDB change streams?
TigerOps does not directly monitor change stream resume tokens but tracks the oplog-related metrics including OplogUsedMB and replication lag. High replication lag is a leading indicator of change stream consumer backlog in DocumentDB.
Stop Discovering DocumentDB Replica Lag After Read Queries Return Stale Data
Cluster health monitoring, replica lag tracking, and AI query anomaly detection. Deploy in 5 minutes.