For a project I'm working on I needed to set labels based on tracing fields. This PR adds support for that (as "dynamic labels") gated behind a default feature. When the feature is disabled, the execution flow is almost unchanged. The code has been tested inside an application both with the feature enabled and disabled and performs as expected.
A single unrelated change here is making the bounded event queue quite a bit larger, into "you have bigger problems if you overflow this" territory - i just found the initial value a bit restrictive. I can remove / split this change into a separate PR if you consider it appropriate.
For a project I'm working on I needed to set labels based on tracing fields. This PR adds support for that (as "dynamic labels") gated behind a default feature. When the feature is disabled, the execution flow is almost unchanged. The code has been tested inside an application both with the feature enabled and disabled and performs as expected.
A single unrelated change here is making the bounded event queue quite a bit larger, into "you have bigger problems if you overflow this" territory - i just found the initial value a bit restrictive. I can remove / split this change into a separate PR if you consider it appropriate.