Skip to content

Conversation

@zacharycmontoya
Copy link
Contributor

@zacharycmontoya zacharycmontoya commented Oct 3, 2024

Description

Apply version tag to a span only if its service name matches the default service name. This may be viewed as a breaking change since now some spans that are started with a new service name will not have the "version" tag set.

Motivation

This behavior conforms to our Config Consistency initiative

Additional Notes

As this may be breaking, we could put this new behavior behind a feature flag, but I'm inclined to say that this is a FIX rather than a FEATURE.

Jira ticket: APMAPI-517

@zacharycmontoya zacharycmontoya changed the title feat: Implement Config Consistency for "version" tag feat: Apply "version" tag only when the span service name matches the default service name Oct 3, 2024
@pr-commenter
Copy link

pr-commenter bot commented Oct 3, 2024

Benchmarks

Benchmark execution time: 2024-10-06 15:23:53

Comparing candidate commit ba34e04 in PR branch zach.montoya/config-consistency/dd-version with baseline commit 85370e7 in branch main.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 1 metrics, 0 unstable metrics.

@codecov-commenter
Copy link

codecov-commenter commented Oct 3, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.66%. Comparing base (85370e7) to head (ba34e04).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #157   +/-   ##
=======================================
  Coverage   94.66%   94.66%           
=======================================
  Files          72       72           
  Lines        3804     3808    +4     
=======================================
+ Hits         3601     3605    +4     
  Misses        203      203           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

…ice name that does not match the tracer default, then no "version" tag is added
…a span only if its service name matches the default service name

Issues: APMAPI-517
@zacharycmontoya zacharycmontoya force-pushed the zach.montoya/config-consistency/dd-version branch from dad1df2 to c544d03 Compare October 3, 2024 22:13
@zacharycmontoya zacharycmontoya changed the title feat: Apply "version" tag only when the span service name matches the default service name fix: Apply "version" tag only when the span service name matches the default service name Oct 3, 2024
@zacharycmontoya zacharycmontoya marked this pull request as ready for review October 3, 2024 22:22
@zacharycmontoya zacharycmontoya requested a review from a team as a code owner October 3, 2024 22:22
@zacharycmontoya zacharycmontoya requested review from dmehala and removed request for a team October 3, 2024 22:22
- Make the logic used to apply `version` tag more explicit.
- Removed unused variable in test.
Copy link
Collaborator

@dmehala dmehala left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM :shipit: I briefly updated the span_data.cpp to make the logic more explicit/easier to comprehend.

@zacharycmontoya zacharycmontoya merged commit ffea35c into main Oct 7, 2024
22 checks passed
@zacharycmontoya zacharycmontoya deleted the zach.montoya/config-consistency/dd-version branch October 7, 2024 12:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants