Datadog
UnverifiedCloud Monitoring as a Service | AI-Powered Observability and Security
TL;DR
Datadog is a comprehensive cloud observability platform for monitoring infrastructure, applications, logs, traces, and security in real-time. It's ideal for DevOps, SRE, and engineering teams managing complex, multi-cloud environments. Key differentiator: unified view across all signals with 750+ integrations and AI-powered insights.
What Users Actually Pay
No user-reported pricing yet.
Our Take
Datadog holds a leading position in the observability market as a go-to SaaS platform for modern cloud-native stacks, powering digital transformation for enterprises worldwide with its end-to-end visibility into metrics, logs, traces, and security. Its primary value proposition is the seamless unification of observability data in one intuitive dashboard, accelerating MTTR (mean time to resolution) and fostering collaboration across DevOps, security, and business teams. With high ratings on G2 (4.4/5), Capterra (4.6/5), and Gartner (4.5/5), it's praised for polished UI, easy agent deployment, and extensive integrations. Strengths include real-time alerting, customizable dashboards, and AI features like Bits AI for investigations, making it stand out for dynamic environments. Reviewers highlight its scalability for thousands of hosts and comprehensive APM capabilities. However, it's not without limitations: pricing is fragmented and unpredictable at scale, often criticized as 'expensive' or a 'Datadog tax' due to per-host, per-GB log ingestion, and custom metric charges—bills can balloon unexpectedly from log spam or high-cardinality data. Best suited for mid-to-large enterprises with budgets for premium observability and complex infrastructures (e.g., Kubernetes, multi-cloud). Smaller teams or cost-sensitive ops may find open-source stacks like Prometheus/Grafana more viable, but Datadog excels where polished, all-in-one reliability is paramount.
Similar Products
Pros
- + Intuitive UI and customizable dashboards for quick insights.
- + Comprehensive integrations (750+) and easy agent setup.
- + Unified observability across infra, apps, logs, traces, and security.
- + Real-time monitoring, alerting, and AI-powered root cause analysis.
- + Scalable for large environments with strong APM and RUM features.
Cons
- - High and unpredictable costs, especially for logs and custom metrics at scale.
- - Complex pricing model with potential bill shocks from usage overages.
- - Vendor lock-in from SDKs and fragmented billing.
- - Occasional performance issues or incomplete docs for edge cases.
- - Not cost-effective for small teams or low-volume usage.
MCP Integrations
2 servers23 tools31 total usesConnect AI assistants to PostgreSQL, MySQL, or SQL Server in 60 seconds. 24 dialect-aware tools — query, schema introspection, anomaly detection, query optimization. Read-only at three layers (firewall + transaction + rules engine).
23 tools
query_sqlExecute a read-only SQL query against the target connection. ONLY SELECT / WITH / EXPLAIN permitted. Write dialect-appropriate SQL for the connection's engine — use PostgreSQL syntax for postgres connections (`SELECT NOW()`, `LIMIT`, `ILIKE`), T-SQL for mssql (`SELECT GETDATE()`, `TOP N`, `LIKE`), MySQL for mysql (`SELECT NOW()`, `LIMIT`). Response meta includes `connection` + `dialect` so you know which syntax worked; reuse that dialect in follow-up calls. Default LIMIT 100 unless the user asks for all rows.describe_schemaDiscover the full database schema: tables, columns, types, primary keys, foreign keys, and indexes. Results cached 1 hour. Call with refresh=true after schema changes.analyze_tableQUICK statistical snapshot for ONE table — row count, null rates, cardinality, numeric min/max/avg, date ranges. Optionally drill into a specific column. Use this for a fast at-a-glance read. Use `data_profile` instead when the user wants a FULL quality report including PII detection and a health score.detect_anomaliesScan a table for unusual patterns: volume drops/spikes, data gaps, value concentration, high null rates, stale data. Severity-ranked alerts. Tables > 100k rows use a sampled path (~5%) — when a finding has `sampled:true`, surface it to the user with a hedge like 'based on a ~5% sample' rather than presenting the number as exact. Dialect-aware: TABLESAMPLE SYSTEM on postgres, TABLESAMPLE PERCENT on mssql, WHERE RAND() on mysql.suggest_queriesGenerate schema-aware query suggestions with ready-to-run SQL. Great for exploring unfamiliar databases or finding useful queries.test_connectionPing a connection (SELECT 1) and return server version + latency. Fast way to confirm credentials and network path without running describe_schema.list_connectionsList every database connection registered for your tenant: name, id, dbType (postgres / mysql / mssql), createdAt. Flags duplicate names — only the first-added connection of a duplicate name is reachable by name. Returns nothing sensitive (no DSN, no credentials).quotaCheck current API usage, daily limit, plan name, and upgrade options.issue_api_keyIssue a fresh ta_data_* API key for your current tenant. Useful for pasting into /add-database or configuring a separate integration. The new key is tied to your existing plan tier. Rate-limited to 5 issuances per tenant per day.explain_queryAnalyze a SQL query's execution plan and return plain-English performance recommendations. Runs EXPLAIN ANALYZE (Postgres) or EXPLAIN FORMAT=JSON (MySQL). [BUILD tier]optimize_querySuggest a rewritten, optimized version of a SQL query with explanations. Identifies sequential scans, missing indexes, sort spills, join inefficiencies, and suggests index DDL. [BUILD tier]data_profileFULL data quality + compliance report for a table: per-column stats PLUS a 0-100 health score, type-gated PII detection (email / phone / SSN / etc.), and insight warnings. Slower than `analyze_table` but returns everything needed to audit a table for ownership / compliance / onboarding. Use this when the user says 'profile' or 'quality report' or mentions PII/compliance. [BUILD tier]query_historyReturn recent queries executed through ThinAir with timing, row counts, and status. [BUILD tier]saved_queriesManage your personal library of reusable SELECT queries. action=save stores a query by name; action=run executes a saved query; action=list returns all your saved queries; action=delete removes one. [BUILD tier]generate_migrationGenerate dialect-correct ALTER TABLE migration SQL + rollback from a plain-English intent. Output uses the connection's exact dialect (ALTER TABLE for all three, plus pg-specific `USING` casts / mssql-specific `sp_rename` / mysql-specific `MODIFY COLUMN`). Never executes. Check response `dialect` field before manually editing — don't hand-translate across dialects. [BUILD tier]generate_seed_dataGenerate realistic, schema-aware INSERT statements for development and testing. Respects types, constraints, and FK relationships. Never executes. [BUILD tier]show_locksList active sessions + blocking locks. Uses the dialect's own system view — `pg_stat_activity` on postgres, `information_schema.processlist` on mysql, `sys.dm_exec_requests` joined with `sys.dm_tran_locks` on mssql. No dialect arg needed — inferred from the connection. **Required privileges (per dialect):** postgres — `pg_read_all_stats` role membership (or be the role that owns the queries; otherwise you only see your own session); mysql — `PROCESS` privilege; mssql — `VIEW SERVER STATE`. If the role lacks the privilege the tool returns a clean `Query blocked by security policy` error rather than partial data — grant the role above and retry. RDS/Aurora/Azure managed PostgreSQL: `pg_read_all_stats` is grantable but not on by default. [BUILD tier]pii_scanSweep string columns across tables for common PII patterns (email, SSN, credit card, phone, JWT, bearer tokens). Heuristic-only — not a compliance guarantee. [BUILD tier]watch_tableMonitor a table's row count and latest record. Compares to previous snapshot to show changes. Built-in scheduler. [ARCHITECT tier]find_n_plus_oneDetect N+1 query patterns from recent query history. Fingerprints queries and flags repeated patterns. [ARCHITECT tier]query_firewallManage per-connection SQL rules: block dangerous patterns, require WHERE on large tables, log PII access. [ARCHITECT tier]impact_analysisAnalyze the blast radius of a proposed schema change: FK dependencies, affected views, row count, risk score. [ARCHITECT tier]cross_db_query⚠️ SQL MUST BE VALID IN EVERY DIALECT YOU TARGET — stick to ANSI-ish SELECT syntax when mixing pg/mysql/mssql. `SELECT TOP 10` (mssql) or `LIMIT` (others) will fail on the wrong side. Run the same query across 2-4 connections in parallel; returns per-connection rows + errors for diffing. Canonical use cases: regional compare (`['mssql-reporting-us', 'mssql-reporting-eu']`), cross-dialect sync check (`['prod-postgres-fleet', 'prod-mysql-app']`), 3-env drift, 4-region compare. Resolve every connection name via `list_connections` first; tool fails per-connection on unknown names. ARCHITECT-tier cap: 4 connections; https://www.thinair.co/ for unlimited. [ARCHITECT tier]
Full Datadog API access: monitors, logs, metrics, traces, dashboards, and observability tools
Last checked May 3, 2026
Compare With
Reviews
No reviews yet. Be the first to review Datadog!