Full observability in one line
No agents to deploy, no config to write. Run a single command and your whole app is instrumented.
Check out anomaly detection in Detective.Try it now
Find the one log that broke your production with full Root Cause Analysis from billions of noisy logs.
Logs
1
Score
0.39
Latest logs
DDL executed: DROP TABLE orders, database=prod-orders-db, user=deploy-bot@internal, rows_affected=1916750, initiated_by=deploy-script
Critical
Yes
Production orders database (prod-orders-db) had 1,916,750 rows deleted via DDL DROP TABLE executed by deploy-bot β likely catastrophic data loss
Summary
A catastrophic DDL event has been detected: `DROP TABLE orders` was executed on prod-orders-db by deploy-bot@internal, destroying approximately 1.9 million rows. This is corroborated by an anomalously low order confirmation rate (only 2 events vs. ~78K normal). S3 backups are confirmed present β immediate on-call response is required to halt the deploy-bot, assess the damage, and restore from backup.
Flagged Clusters (2)
A DDL 'DROP TABLE orders' statement was executed against prod-orders-db by deploy-bot@internal via a deploy-script, affecting 1,916,750 rows. This appears to be an unintended or malicious table drop/truncation on the production orders database. Given the volume (nearly 2M rows), this likely represents complete or near-complete destruction of the live orders table. Immediate incident response is required: halt deploy-bot, verify backups (cluster 31 shows backups exist in S3), and initiate restore procedure.
Only 2 CONFIRMED order status transitions were logged β anomalously low compared to the 78,386 status transitions in cluster 13. This sharp drop in order confirmations is consistent with the orders table having been deleted (cluster 1), as new writes/reads would fail or return empty after the DDL event.
Recommended Actions
IMMEDIATELY revoke deploy-bot@internal credentials and halt all deploy-script executions to prevent further destructive DDL operations
Identify the most recent successful backup from S3 (cluster 31 confirms backups to s3://backups/) and initiate point-in-time restore of prod-orders-db
Audit deploy-script source code and CI/CD pipeline to determine how a DROP TABLE DDL targeting prod was triggered β check for environment misconfiguration or compromised credentials
Verify application health: query prod-orders-db to assess actual table state (dropped vs truncated vs partially deleted) before restore to choose the correct recovery path
After restore, add DDL guardrails to prod-orders-db: revoke DROP/DELETE TABLE privileges from deploy-bot, require manual approval for destructive DDL via change management
Supports 100+ telemetry datasources
No agents to deploy, no config to write. Run a single command and your whole app is instrumented.

We use ML to condense billions of logs into small snapshots, so your LLMs can root cause from these snapshots instead of blowing up tokens.
Learn moreStart free. No credit card. No YAML.
Free Trial
Full access for 7 days, no card required.
Pro
Everything you need to stop looking at logs.
Enterprise
On-prem, SLAs, and dedicated support.
Fast-moving teams use Rocketgraph every day. Join them.