This pull request adds the ability to set the span name in the transformation filter.
We add a new field in the transformation template to allow setting modifying the span. The new field currently only accepts the span name as a field, but attributes/baggage/other data could also be added as fields to be modified here as well.
If route.decorator.operation is set, we should not update the field in this filter - we intend for the operation field to take precedence over this value, which is set at the virtual host level and intended to be used as a default instead.
Here is an envoy configuration for testing - note the presence of route.decorator.operation, and how uncommenting it causes Envoy to use that field as the span name instead of the hostname.
This pull request adds the ability to set the span name in the transformation filter.
We add a new field in the transformation template to allow setting modifying the span. The new field currently only accepts the span name as a field, but attributes/baggage/other data could also be added as fields to be modified here as well.
If
route.decorator.operation
is set, we should not update the field in this filter - we intend for the operation field to take precedence over this value, which is set at the virtual host level and intended to be used as a default instead.Here is an envoy configuration for testing - note the presence of
route.decorator.operation
, and how uncommenting it causes Envoy to use that field as the span name instead of the hostname.