diff options
author | 2024-03-04 05:10:15 -0500 | |
---|---|---|
committer | 2024-03-04 11:10:15 +0100 | |
commit | 66d9297e64fdc9fb4bf4b8df3ea88c1e412aa43c (patch) | |
tree | 0e133415a9d1cddf6b18a5cf958aea4962d0668b /internal/ap/normalize.go | |
parent | [chore]: Bump golang.org/x/crypto from 0.19.0 to 0.20.0 (#2716) (diff) | |
download | gotosocial-66d9297e64fdc9fb4bf4b8df3ea88c1e412aa43c.tar.xz |
[bugfix/tracing] fix broken tracing due to conflicting schema url (#2712)
The OpenTelemetry SDK is very strict about the schema version when
the `Resource` is initialized.
Specifically, different schema versions _CANNOT_ be mixed, and since
the default SDK resource (which is merged with the user-defined one)
defines a schema URL, the `semconv` imports are really prone to being
out-of-sync.
The best way to avoid this is to merge a _schemaless_ resource. This
is fine...there's plenty of other ways to get `semconv` out of sync,
and the core service attributes (e.g. `service.name`) should not ever
change.
Additionally, any errors here are now propagated so that they'll be
visible instead of silently swallowed.
Diffstat (limited to 'internal/ap/normalize.go')
0 files changed, 0 insertions, 0 deletions