Daniel Dyla
Daniel Dyla
@toumorokoshi I was saying the primary use of `isRecording` is to avoid expensive operations to gather span attributes. @Oberon00 had recommended checking the context for instrumentation disabled flag within instrumentations...
>I think I understand. You're referring to adding a check, per integration, to see if the IsRecording flag is set. if it's false, then we avoid adding attributes altogether, which...
I created a PR based on the discussion from the SIG #1653 The discussion was primarily around clients creating and exporting APIs that were not specified and how to do...
> @dyladan was there a decision around what the right way to move forward for suppressing instrumentations? I see the proposed solution of making a key available through the API...
> May I get a short summary regarding why feature-flagging needs to be part of semantic conventions? Is there an example (I read through the linked [issue](https://github.com/open-feature/spec/issues/30) and couldn't find...
> > If feature flag keys and values are consistently reported, it will enable splitting traces and metrics by these values for usecases like A/B testing, feature rollouts, and similar....
This is not stale
> @beeme1mr > > One thing that may be worth adding is a `evaluation_reason` or something similar. This would identify _why_ a particular flag value was returned (some targeting rule...
> > 1. I can't see what obvious value that provides. Knowing that a flag is `true` because it targets specific users is possible from just the key and the...