MongoDB vs Firestore

Audits WiredTiger read/write available tickets, queries the system profiler for slow operations (>100ms), and checks for locked operations.

# 1. Inspect concurrent transaction read/write tickets in WiredTiger
mongosh --eval '
const tickets = db.serverStatus().wiredTiger.concurrentTransactions;
print("Read Tickets Available:  " + tickets.read.available);
print("Read Tickets Out:        " + tickets.read.out);
print("Write Tickets Available: " + tickets.write.available);
print("Write Tickets Out:       " + tickets.write.out);
'

# 2. Query slow operations exceeding 100ms from the profiler
mongosh --eval 'db.system.profile.find({millis: {$gt: 100}}).sort({ts: -1}).limit(5).pretty()'

# 3. Identify transactions waiting for write locks or holding locks > 5s
mongosh --eval 'db.currentOp({"active": true, "secs_running": {"$gt": 5}, "waitingForLock": true})'

Queries Firestore read rate metrics, monitors write contention error spikes, and audits composite index builds.

# 1. Query Firestore document read rates across active GCP project via Cloud Monitoring
gcloud monitoring time-series read \
  "firestore.googleapis.com/document/read_count" \
  --window="1h" \
  --aggregation="ALIGN_RATE"

# 2. Check for RESOURCE_EXHAUSTED or ABORTED write contention error spikes
gcloud logging read \
  'resource.type="cloud_firestore_database" AND severity>=ERROR' \
  --limit=10 \
  --format="table(timestamp, jsonPayload.status.code, jsonPayload.status.message)"

# 3. Audit active composite index status and build states
gcloud firestore indexes composite list --format="table(name, state)"