Remove full schema collection from Kafka, Avro, and Protobuf instrumentation#12038
Remove full schema collection from Kafka, Avro, and Protobuf instrumentation#12038piochelepiotr wants to merge 2 commits into
Conversation
…ntation Data Streams Monitoring no longer extracts and reports full Avro/Protobuf schema definitions from traced messages. This removes the avro-1.11.3 and protobuf-3.0 instrumentation modules, the AvroSchemaExtractor used by the Kafka producer instrumentation, and the associated schema-building/sampling core in dd-trace-core and internal-api. Schema Registry utilization tracking (confluent-schema-registry) is untouched and continues to report schema ID/registry usage for DSM lineage. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
🎯 Code Coverage (details) 🔗 Commit SHA: 9cf8108 | Docs | Datadog PR Page | Give us feedback! |
…grations Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
🟢 Java Benchmark SLOs — All performance SLOs passed
PR vs. master results
Commit: Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9cf8108ec5
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| @@ -33,13 +33,6 @@ public class DDTags { | |||
| public static final String THREAD_ID = "thread.id"; | |||
| public static final String DB_STATEMENT = "sql.query"; | |||
| public static final String PATHWAY_HASH = "pathway.hash"; | |||
There was a problem hiding this comment.
Preserve deprecated schema tag constants
When downstream instrumentation or user code compiles against dd-trace-api and imports any of the DDTags.SCHEMA_* constants, deleting these public constants turns a deprecated data-streams feature removal into a source-compatibility break even though the agent can simply stop emitting the tags. Please keep the constants, likely marked deprecated, until a planned breaking API release.
AGENTS.md reference: AGENTS.md:L12-L16
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
More details
Every removal is complete and consistent: no dangling callers of trySampleSchema/canSampleSchema/getSchema, no imports of the deleted Schema/SchemaIterator/SchemaBuilder API types, no references to the removed DDTags.SCHEMA_* constants, and all three AgentDataStreamsMonitoring implementations are in sync with the slimmed interface. The schema-registry utilization path (reportSchemaRegistryUsage, confluent-schema-registry-4.1) is untouched and correct.
📊 Validated against 8 scenarios · Open Bits AI session
🤖 Datadog Autotest · Commit 9cf8108 · What is Autotest? · Any feedback? Reach out in #autotest
sarahchen6
left a comment
There was a problem hiding this comment.
LGTM pending the system tests update
Summary
avro-1.11.3andprotobuf-3.0instrumentation modules, theAvroSchemaExtractorused by the Kafka producer instrumentation (kafka-clients-0.11,kafka-clients-3.8), and the supporting schema-building/sampling core (SchemaBuilder,SchemaSampler,Schema,SchemaIterator) indd-trace-core/internal-api.DDTags.SCHEMA_*span tags (SCHEMA_DEFINITION,SCHEMA_WEIGHT,SCHEMA_TYPE,SCHEMA_ID,SCHEMA_TOPIC,SCHEMA_OPERATION,SCHEMA_NAME).reportSchemaRegistryUsage) is intentionally untouched — that is a separate feature (detecting registry usage/schema ID for DSM lineage) and continues to work as before.Test plan
kafka-clients-0.11andkafka-clients-3.8test suites (dropped theschemaparam and assertions fromproducerSpan()helpers; removed the standalone avro-schema-extraction test).SchemaBuilderTest/SchemaSamplerTestand theschemaSamplerSamplesWithCorrectWeightstest inDefaultDataStreamsMonitoringTest, keeping all schema-registry-usage tests intact.dd-trace-coredatastreams tests,kafka-clients-0.11tests,kafka-clients-3.8tests, andconfluent-schema-registry-4.1compile all pass./techdebtand/perf-reviewskills over the branch diff — no findings.🤖 Generated with Claude Code