Damien Mathieu
Damien Mathieu
I think looking at your other proposals would be nice.
Keeping a list of multiple endpoints is something that would break the specification requirements for OTLP exporters. https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/protocol/exporter.md#configuration-options Also, if we start doing that, it's a feature we're introducing to...
@sh0rez can this be closed?
This is now invalid, since we don't have the dup option anymore.
This issue hasn't been updated in quite some time. Unassigning it so someone else can pick it up.
We should keep things simple. We currently have breaking changes because we used semantic conventions that were not stable yet. The state of the HTTP semantic conventions is now that...
You don't need a new interface. The behavior you describe is kinda what we already do for traces. For example: https://github.com/open-telemetry/opentelemetry-go-contrib/blob/04815fd8f28277a6ec7ff21d29e49a6b9558370e/instrumentation/net/http/otelhttp/internal/semconv/env.go#L51-L56 For RecordMetrics, you would need something like this: ```golang...
The two fixes here could be to get https://github.com/lycheeverse/lychee/pull/1403 to move forward, so a links check that fails would still update the cache with URLs that succeeded, making retries only...
This has been fixed in https://github.com/open-telemetry/opentelemetry-go-contrib/pull/6323
This hasn't been updated in quite a while. Unassigning so someone else can pick it up (feel free to open a PR and link this issue in it, assignments are...