Skip to content

gRPC-1.5 instrumentation: regenerated via RPC-category readiness loop - #12417

Draft
jordan-wong wants to merge 3 commits into
masterfrom
eval/grpc-rpc-verify3b-rebased-20260904
Draft

gRPC-1.5 instrumentation: regenerated via RPC-category readiness loop#12417
jordan-wong wants to merge 3 commits into
masterfrom
eval/grpc-rpc-verify3b-rebased-20260904

Conversation

@jordan-wong

Copy link
Copy Markdown
Contributor

Summary

  • Blind-regenerated gRPC-1.5 client/server instrumentation from scratch, produced by the apm-instrumentation-toolkit's RPC category readiness loop (cycle 1).
  • Verifies two gating rules against a full clean-delete regen: no scope-narrowing/silent omission of pre-existing instrumentation targets (R-RPC-1), and a correct client/server tag contract — distinct component, span.kind, and status tags per side (R-RPC-2).
  • QueuedCommandInstrumentation (a Netty write-queue profiling hook with no client/server call-path overlap) is explicitly re-created rather than silently dropped, per the loop's per-file enumeration rule.

Test plan

  • CI green on this branch
  • Confirm gRPC client/server spans still carry component, span.kind, rpc.service tags as expected
  • Confirm no regression vs master's existing gRPC test coverage

🤖 Generated with the apm-instrumentation-toolkit RPC category readiness loop.

@jordan-wong jordan-wong added tag: ai generated Largely based on code generated by an AI or LLM tag: apm integration toolkit Changes generated by DataDog/apm-instrumentation-toolkit as part of IDM AIT experimentation labels Sep 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

tag: ai generated Largely based on code generated by an AI or LLM tag: apm integration toolkit Changes generated by DataDog/apm-instrumentation-toolkit as part of IDM AIT experimentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant