feat(traces): use DD_SERVICE for inferred spans when integration service names are removed

[zarirhamza]

Summary

• Adds DD_TRACE_REMOVE_INTEGRATION_SERVICE_NAMES_ENABLED (default false). When it is set and DD_SERVICE is configured, inferred (synthetic) event-source spans report the function's base service instead of the AWS resource/instance representation.
• An explicit DD_SERVICE_MAPPING entry still takes precedence.
• Applies to the wrapped inferred spans too (SQS→SNS, SQS→EventBridge, SNS→EventBridge).

Motivation

Customers currently need one DD_SERVICE_MAPPING entry per trigger type per function to get their event-source spans onto their own service name. This gives them a single setting that consolidates all of them at once.

Tracked by FRSLES-869. This repo is the only inferred-span implementation for Go, Java, .NET, and Ruby, which delegate inference to the extension entirely. Companion PRs: datadog-lambda-python#834, datadog-lambda-js#814.

Implementation note

Rather than thread two more parameters through Trigger::enrich_span and resolve_service_name (a ~200-line mechanical change across all 13 trigger modules and their tests), the override is applied in span_inferrer.rs immediately after enrichment.

To keep DD_SERVICE_MAPPING precedence expressed in one place, Trigger gains a default has_service_mapping_entry method that reuses the same specific/generic identifiers resolve_service_name looks up. Happy to switch to the full parameter-threading approach if reviewers prefer a single resolution ladder.

The override lowercases DD_SERVICE to match the invocation span built in processor.rs, so both spans land on the same service.

Scope

Service-name resolution only. complete_inferred_spans still sets peer.service to the invocation span's service as it does today; revisiting that pairing is deliberately left to a follow-up.

Test plan

• 6 new tests in span_inferrer.rs: override applies, disabled by default, yields to DD_SERVICE_MAPPING, no-op without DD_SERVICE, lowercases DD_SERVICE, applies to wrapped spans
• 3 new config tests: default off, from env, from YAML
• cargo test --lib — 550 passed
• cargo clippy --lib --tests -- -D warnings clean
• cargo fmt --check clean

[Copilot]

Pull request overview

Adds an opt-in configuration that, when enabled and DD_SERVICE is set, forces inferred (synthetic) trigger spans (including wrapped spans) to report the function’s base service instead of the trigger’s AWS resource/instance-derived service—while preserving DD_SERVICE_MAPPING precedence.

Changes:

• Introduces DD_TRACE_REMOVE_INTEGRATION_SERVICE_NAMES_ENABLED (false by default) and wires it through env/YAML config loading.
• Adds a post-enrichment override in span_inferrer.rs to set inferred-span service from DD_SERVICE unless an explicit service mapping exists.
• Adds unit tests covering default behavior, override behavior, mapping precedence, and wrapped-span behavior.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
bottlecap/src/lifecycle/invocation/triggers/mod.rs	Adds a helper on Trigger to detect whether DD_SERVICE_MAPPING targets a trigger (specific or generic key) to preserve precedence.
bottlecap/src/lifecycle/invocation/span_inferrer.rs	Applies the new base-service override to inferred spans and wrapped inferred spans; adds targeted tests.
bottlecap/src/config/mod.rs	Adds the new Lambda extension config flag with defaults and env/YAML parsing, plus config tests.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[datadog-prod-us1-5]

⚠️ Warnings

❌ Your PR has failed checks. Please review the issues below and take necessary action before merging.

🚦 1 Pipeline job failed

DataDog/datadog-lambda-extension | e2e-test-status (amd64)

View more details · View in GitLab

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: fc3b16e | Docs | View more details | Give us feedback!}