Bryan Boreham

@delve you may need a newer collector - see https://www.jaegertracing.io/docs/1.21/opentelemetry/ However that support is marked experimental.

I commented on the PR, but this issue seems to be describing something slightly different to what I understood from the PR. Can you give an example of user attributes...

Thanks, "cluster name" and "environment" make sense. I can see both sides of adding more info about kspan - it would be useful for debugging, but also make the display...

Thanks for the report. Shouldn’t that be filed as an XRay incompatibility with OpenTelemetry?

It is feasible to change the scheme kspan uses, at the cost of losing trace continuity across a restart of kspan. Or add some persistence mechanism to cover the restart.

Hello, and thank you for your interest. I expect Kspan will work on OpenShift, although I have not tried it. The only network access Kspan needs is to the Kubernetes...

You can change the address with a command-line flag `-otlp-addr=:`. This would go under `args:` in the pod manifest, if you continue the style of the blog post.

Conceptually, yes. In some ways it should be better than Events, since we could get a better start/end timestamp. But in practice it seems we don’t always get each update,...

I'm doing ok with this config: ``` tempo: configs: - automatic_logging: roots: true span_attributes: ["namespace", "object"] ```

Guessing this was posted in the wrong place.