John Watson
John Watson
the semconv doc needs to be updated to pointed to the new semconv artifact from the new semantic conventions repo, FYI: ``` implementation("io.opentelemetry.semconv:opentelemetry-semconv:1.23.1-alpha"); ```
Since the logging exporter is only intended to be used for very rough, simple debugging, I doubt we would want to make the output style configurable. You are welcome to...
Our support for numbers (long, double, int) are only primitives, so we'd have to figure out what type the number is and cast down to the primitive type.
This is not something that is specified as a part of OpenTelemetry. If you need something new, I recommend opening an issue in the specification.
> Thanks a lot for your comments. @jkwatson . Sorry I am not familiar with the process as it is my first time opening an issue . Could you please...
For two reasons, I think we would not consider making this addition: 1. We strongly recommend that you pre-allocate your attribute keys, to avoid extra runtime allocations 2. This would...
@gavin-nia If you have time for a PR that addresses the issue, that would be fantastic. Jack is very over-burdened, and not an open-census user, so it would be great...
In general, the Resource is not something that is supposed to be mutable like this, especially not in the middle of processing a span. If we were to add a...
@carlosalberto Can you take a look? This doesn't seem out-of-line to me, but I really don't know much about OT.