February 2026 monthly highlights for DataDog/integrations-core: Implemented new MongoDB query metrics collection using $queryStats (MongoDB 8.0+) and prepared the integration for enhanced query performance monitoring.

January 2026 monthly summary for DataDog/integrations-core. Delivered Data Collection Reliability for Instrumentation and SQL Server Integration, consolidating instrumentation reliability improvements and stability fixes to improve data accuracy and monitoring reliability for SQL Server integration. Implemented guard to skip sample and explain plan collection when statement timer instrumentation is not enabled to reduce overhead. Key fixes included addressing a KeyError in pg_stat_statements plan/timing tracking settings and preventing STRING_AGG truncation for tables with many columns. These changes reduce data gaps, lower operational toil, and improve reliability for SQL Server metrics.

October 2025 monthly summary: Delivered privacy- and reliability-focused enhancements across the DataDog agent and integrations-core. Implemented configurable SQL bind parameter obfuscation to mask parameters with a placeholder for enhanced data privacy, extended the SQL Server obfuscator with a replace_bind_parameter option, introduced MySQL AWS RDS IAM token auto-refresh to prevent disruption, and improved tagging consistency by normalizing SQL Server tags to lowercase. These changes reduce data exposure risk, improve telemetry cleanliness, and enhance connection stability for customers relying on SQL Server and MySQL deployments.

September 2025 performance summary: Focused on enhancing developer experience and data consistency across DataDog/documentation and DataDog/integrations-core. Key features delivered include documentation guidance for capturing SQL query parameter values and optional tag normalization in TagManager. No major bug fixes were logged in this period. Overall impact: improved onboarding and data quality, clearer guidance for users, and more robust tagging semantics. Technologies demonstrated: documentation indexing, unit testing, and TagManager normalization logic, with changes tied to commits 29f97e453fe81513e54c4b0ee4e33998000bd81e and 5664f987eaac920118e8e5cfef5322819bc68b26.

July 2025 monthly summary: Focused on stability, forward-compatibility, and observability across core data integrations and language bindings to drive faster migrations, improved query analysis, and stronger trace integrity. Key outcomes include backward-compatible deprecation and rename of DBM config options, expanded secondary-visibility through index statistics, UTC correctness for MongoDB system.profile, enhanced tracing taxonomy with db.type tagging for PDO, and fixes to prevent trace context duplication in SQL trace injection.

June 2025 monthly summary for DataDog/integrations-core and DataDog/documentation. Delivered feature enhancements for SQL Server and MongoDB integrations, implemented stability and configuration improvements, and updated DBM-related documentation to reflect expanded coverage. These efforts improved observability, reliability, and upgrade safety while expanding product documentation for Database Monitoring (DBM). Impact highlights: - Observability and debugging: richer SQL Server activity payload with client_interface_name to provide finer client context and faster issue diagnosis. - Reliability and resource management: enforced maxTimeMS on all MongoDB API calls and collectors, reducing long-running operations and guarding against resource exhaustion. - Configuration and maintainability: introduced collect_schemas config option and deprecated schemas_collection with a backward-compatible path, including tests to validate deprecation behavior. - Documentation coverage: added a new DBM integrations category in High Availability docs with links to supported DBM pages, improving discoverability for operators. Overall, the month delivered concrete value through feature delivery, stability improvements, and clearer upgrade paths, supported by targeted tests and clearer documentation.

May 2025 monthly summary: Focused on expanding observability for databases and improving performance of the obfuscation path across two DataDog repositories. Delivered MongoDB Datadog DBM/APM integration with dd-trace-py, updated docs with setup instructions and Python examples. Implemented SQL Obfuscator cache key optimization in datadog-agent, computing the cache key only when caching is enabled and adding a deferred cache write after obfuscation to reduce unnecessary work when cache is disabled. These efforts broaden monitoring visibility, reduce runtime overhead, and streamline onboarding for developers. Technologies used include Python instrumentation, dd-trace-py integration, caching strategies, and thorough documentation across DataDog/documentation and DataDog/datadog-agent.

April 2025: Cross-DBM monitoring, observability, and configuration improvements across DataDog products. Delivered cross-DBM High Availability (HA) support across MongoDB, MySQL, PostgreSQL, and SQL Server; enhanced PostgreSQL statement metrics with a new derivative metric (calls) and smarter indicators to reduce false positives; enabled DBM propagation for PyMongo to correlate database operations with application traces; fixed critical MongoDB monitoring explainability and shard-robustness issues; resolved tag duplication after MySQL failover; introduced an Oracle HA support indicator and simplified Oracle integration configuration; maintained alignment on OpenSSL usage.

March 2025 was a stability and observability sprint across agents, tracers, and docs. Key outcomes include: 1) SQL parsing stability: upgraded go-sqllexer to v0.1.3 to fix a trimQuotes panic across the SQL parsing path; 2) MongoDB Core Plugin correctness: preserved DBM comments when dbmPropagationMode is disabled, with new checks and tests; 3) MongoDB Explain Plan enhancements in integrations-core: added queryPlanner verbosity mode, default verbosity to queryPlanner, avoided full explain for certain commands, and adjusted collection stats cadence; 4) FK metadata and system stats improvements: added a config option to skip system DB stats and extended foreign key delete/update metadata collection for MySQL/MariaDB and SQL Server with tests; 5) MariaDB 11.4 support updates: refreshed docs and test matrix to include 11.4 LTS and drop EOL versions. Maintenance and cleanup included reverting MongoDB agent service tag and removing Python 2017 support on Linux for SQL Server.

February 2025 performance summary focusing on feature delivery, bug fixes, and performance improvements across core DataDog repos. Highlights include MongoDB lsid/transaction data collection, arbiter host metrics skip, MySQL dbms_flavor tag dedup, PyMongo 4.11 upgrade, MongoDB tracer propagation improvements, MongoDB docs update, and performance-oriented go-sqllexer upgrades affecting datadog-agent. Business value includes improved data fidelity, reduced noise, safer host metrics collection, and improved runtime efficiency.

January 2025 — Monthly summary Key features delivered: - PostgreSQL Monitoring: Rich index metadata collection (uniqueness, exclusion, immediacy, clustering, validity, partial status) and support for emitting raw non-prepared query statements. Commits: d890a1fa079348ca96827552af12cef011998812; 40de494c0e68fdf479410e151404ad90198ff646 - MongoDB Integration Enhancements: zlib compression support, optional Atlas search indexes collection, increased cadence for schema/index data to 1 hour, improved activity samples including explain operations, added service tag to agent operations, and updated DBM docs. Commits include: 3c91dad80880745b9703d15443ebba9942a8e43b; 5dc1c5c211f9a4e9479fc20c35a707a873281e51; 58e21f732e0c827ae211019efb8fb68c78793110; b3da55a32eb2ca2754cb2522ba57dbd0d3490c39; 6c5362ed47c57f1fb1119b8015c5ab59c9e1d01a; 3a892cb5cca689cf5ae0a7bfe420d0880b8b76ea - SQL Server Monitoring Enhancements: Emit raw query statements and expose raw plan information (raw_signature) for non-prepared statements. Commits: 5150864e6505ece89c4097ca594e71cbc2fca1a9; a1cebab89763d7a7cc7a0725dd7b6f6f58e95691 - MongoDB Oplog Stats Bug Fix: CommandCursor not subscriptable; fix by converting stats to a list before access. Commit: fd08ef97a350e2a2e8a444f2678c4f66928c73c9 - DataDog Agent: Cache item size calculation corrected for obfuscated SQL queries to include struct overhead, improving memory usage estimates. Commit: 6afa0950586759bacd2fef346d2ff8aa4eca6f63 Major bugs fixed: - PostgreSQL: Fixed duplicate rows in QUERY_PG_CLASS by filtering out relations with AccessExclusiveLock (and added tests). Commit: 6e79f147abae8b7053f69e5876529cfa7bc01c7f - SQL Server: Fixed case-insensitive database names handling during schema collection. Commit: 8af850dd9bb18b8f6e7ad98c5be2444d73069a99 - MongoDB Oplog Stats: Resolved CommandCursor not subscriptable issue related to collection stats. Commit: fd08ef97a350e2a2e8a444f2678c4f66928c73c9 - Documentation: Clarified MongoDB slow operations collection when database profiling is disabled and documented the getLog limitation (1024 events). Commit: e687b4674fabd49d68a2060de07f4c3b88d2ccf6 Overall impact and accomplishments: - Improved observability, forensics, and reliability across core data stores, enabling deeper diagnostics and faster investigation. - Reduced data gaps and duplicates, more predictable data collection cadence, and better memory estimation for obfuscated queries. - Enhanced developer efficiency through tagging and clearer documentation, supporting governance and onboarding. Technologies/skills demonstrated: - PostgreSQL, MongoDB, and SQL Server monitoring; data collection enhancements (raw queries, raw plans, index metadata), compression (zlib), configurable data cadence, testing, and documentation updates.

December 2024: Focused on reliability, observability, and dependency stability across core integrations and the agent to drive higher data quality and reduced runtime errors. Key features delivered include: MongoDB Integration Robustness (skip unauthorized system collections to prevent collStats/indexStats errors; updated collectors and fixtures), PostgreSQL Integration Observability and Configuration (debug logging for truncated queries, track_activity_query_size guidance, and improved truncation reporting with query signature), and a cross-repo dependency update (Go-sqllexer to v0.0.18 across DataDog/datadog-agent). Major bugs fixed: prevented collStats/indexStats execution on unauthorized local DB collections, eliminating permission-related failure modes. Overall impact: higher robustness of data collection, improved visibility into long-running queries and thresholds, and stabilized dependencies across the stack. Technologies/skills demonstrated: Python-based collectors and fixtures, Go module management, enhanced logging/observability, test fixtures, and cross-repo collaboration.

November 2024 performance summary: Delivered substantial DBM improvements across MongoDB, SQL Server, MySQL, and PostgreSQL, strengthened reliability, expanded cross-region testing, and updated documentation. Key outcomes include enhanced MongoDB monitoring with queued read/write monitors and configurable collection intervals, reliability improvements (timezone-aware slow query logs and recovery handling), SQL Server improvements (opt-in aggregate_sql_databases, non-UTC test coverage) and DBM metrics gating and naming fixes, MySQL dbms_flavor tagging, PostgreSQL AlloyDB autodiscovery exclusions, CI stability improvements, and expanded docs for MongoDB and Amazon DocumentDB DBM.

October 2024 (Month: 2024-10) focused on strengthening observability, telemetry fidelity, and reliability in the integrations-core MongoDB-related workloads for bhargavnariyanicrest/integrations-core. Key features delivered include Datadog DBM enhancements with integration-level service tagging and Amazon DocumentDB cloud metadata emission for MongoDB, plus performance and reliability improvements through MongoDB explain plan skip optimization. A robust database name parsing fix supports older MongoDB versions, and CODEOWNERS realignment clarifies ownership of the MongoDB integration. Collectively, these efforts improve telemetry fidelity, reduce unnecessary workloads, and clarify ownership, enabling faster incident response and improved product telemetry.