Populate source.name and source.version on flag_evaluations and exposures EVP

[vjfridge]

Summary

The Java server SDK emits flag_evaluations and exposures EVP data via FeatureFlagEvpPublisher → /api/v2/flagevaluation, but did not populate the SDK/tracer name or version on the payload. Grep of products/feature-flagging for source.name, source.version, telemetry.sdk.*, sdk.version returned zero matches.

Change

FeatureFlagEvpContext.from builds the top-level context map shared by both the flagevaluation and exposures EVP writers (FlagEvaluationWriterImpl and ExposureWriterImpl both call it). Add two keys:

• source.name → "dd-trace-java" (new SOURCE_NAME constant)
• source.version → TracerVersion.TRACER_VERSION (existing build-time constant, read from the dd-java-agent.version resource — the same value the telemetry module sends as tracer_version on heartbeats)

Because the context map is shared, this single change populates the source.name / source.version facets on both EVP streams.

Prior art

TelemetryRequestBody (telemetry module) already sends tracer_version and language_name on every telemetry request. This reuses the same TracerVersion.TRACER_VERSION constant — no new version-lookup machinery.

Testing

• ./gradlew :products:feature-flagging:feature-flagging-lib:test ✅
• ./gradlew :products:feature-flagging:feature-flagging-lib:spotlessCheck ✅
• Updated ExposureWriterTests.assertContext to assert source.name and source.version (referencing TracerVersion.TRACER_VERSION so the assertion is environment-agnostic).

Jira

• FFL-2995 — Java evp flag_evaluations emit sdk name and version
• Related: FFL-2996 (service version facet), FFL-2503 (client SDK source.name/version), FFL-2446 (Java EVP flagevaluation writer)
• Roadmap: Feature Flag Observability Telemetry Roadmap

Generated with Claude Code

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	14.88 s	14.78 s	[-0.3%; +1.6%] (no difference)
startup:insecure-bank:tracing:Agent	13.59 s	13.77 s	[-2.0%; -0.5%] (maybe better)
startup:petclinic:appsec:Agent	17.56 s	17.33 s	[+0.5%; +2.2%] (maybe worse)
startup:petclinic:iast:Agent	17.52 s	17.64 s	[-1.4%; +0.1%] (no difference)
startup:petclinic:profiling:Agent	17.46 s	17.44 s	[-0.9%; +1.2%] (no difference)
startup:petclinic:sca:Agent	17.45 s	17.20 s	[+0.5%; +2.4%] (maybe worse)
startup:petclinic:tracing:Agent	16.14 s	16.70 s	[-7.7%; +1.0%] (no difference)

Commit: 4aa5a6f9 · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.