Summary
Because of limitations of joins between Transaction and Span data, I'd like to be able to add custom attributes (eg. "team name" or even transaction name) to ALL spans following a call to newrelic_add_custom_span_parameter, rather than only the one span going on when I call that function.
Desired Behavior
Ideally, adding a custom attribute on a span could be added for just that one span, or for all spans that follow that one.
Possible Solution
newrelic_add_custom_span_parameter could accept an optional boolean with default false, that when set true would propagate that custom attribute to all future spans for that transaction.
Additional context
We have a monolithic codebase and many different teams call certain areas of the code. There is one "appName" with 45+ teams contributing, and it would be very helpful to find which team is abusing use of some area of the code if we can more easily facet by teamName for instance.
Summary
Because of limitations of joins between Transaction and Span data, I'd like to be able to add custom attributes (eg. "team name" or even transaction name) to ALL spans following a call to newrelic_add_custom_span_parameter, rather than only the one span going on when I call that function.
Desired Behavior
Ideally, adding a custom attribute on a span could be added for just that one span, or for all spans that follow that one.
Possible Solution
newrelic_add_custom_span_parameter could accept an optional boolean with default false, that when set true would propagate that custom attribute to all future spans for that transaction.
Additional context
We have a monolithic codebase and many different teams call certain areas of the code. There is one "appName" with 45+ teams contributing, and it would be very helpful to find which team is abusing use of some area of the code if we can more easily facet by teamName for instance.