The name "IsRecordingEvents" misleading as it represent recording of any information, not just Events

[SergeyKanzhelev]

The semantics of IsRecordingEvents is not only about recording events but also setting attributes.

Should it be called IsActive?

[bogdandrutu]

Active may be confusing especially with being active in the context. So I would suggest maybe IsRecording?

[SergeyKanzhelev]

I'm good with IsRecording

[spidergears]

IsAlive, if not alive its dead, dead don't record, they walk though.

[SergeyKanzhelev]

Perhaps we need to clarify semantics of this flag even further. For instance, will name be recorded on span? There may be vendors who need to get the span name and serialize it to the wire. Even when span wasn't recorded. Do we really want to not record attributes?

[jmacd]

This feels low priority, but I would use the most concretely applicable term possible.
It's possible for an implementation that performs tail sampling in process to use a real span that may or may not be recorded. We might call this "IsNoOp" or "IsTraced".

[SergeyKanzhelev]

I changed title to explain where the confusion can be from. IsRecordingEvents responsible for more than just events recording. So I'd suggest to change the name to IsRecording as a minimal first step. Happy to discuss further for alternative names.

[tedsuo]

I'm fine with IsRecording, though perhaps IsEnabled might avoid some confusion for cases like tail-based sampling, where you don't technically know if the span will be recorded or not.

[SergeyKanzhelev]

IsRecording is used to record something even if it was sampled out. In case of tail based sampling I'd think sampled flag will be true anyway and will set recording to true automatically.