Hey there,

I was interested in setting up tracing for an existing Concourse deployment although I am hesitant to capture full traces given that, as a user, it isn't immediately clear how many spans I can expect Concourse to create.

My next step would be to set a sampling rate using an environment variable however I wouldn't expect that to work given that a 100% sample rate is currently hardcoded.

The Go SDK for OpenTelemetry checks enivironment variables first before overriding discovered values with hardcoded values which is described here but can also be observed in code as well.

According to the documentation, the default value is to always sample:

By default, the tracer provider uses a ParentBased sampler with the AlwaysSample sampler.

Given that, it should be fine to remove the hardcoded AlwaysSample rule which will retain the same behavior while unlocking the ability to introduce a sample rate via environment variable