Add `endpoint` attribute to otlp exporter by theSuess · Pull Request #14998 · open-telemetry/opentelemetry-collector

theSuess · 2026-03-24T10:44:07Z

Description

This PR exposes the endpoint value of the otlp and otlphttp exporter components to the metrics generated by these exporters.

This is useful for operators of the collector to observe data flow to different endpoints across large numbers of collector instances without having to cross-reference the specific configuration per instance.

The implementation extends the exporterhelper with a new option WithAttrs that allows developers of exporters to add extra labels to metrics produced. This allows for more flexibility for implementers of exporters to add attributes that might be relevant in the specific use case.

Testing

Added tests to ensure attributes passed with the new option are recorded correctly
Tested a build of this branch by configuring the collector to receive OTLP and export it to another collector. The new endpoint shows up correctly.

Documentation

Assuming this change is accepted, I'll create a PR to update the internal telemetry page in the OpenTelemetry documentation

theSuess · 2026-03-24T10:45:47Z

If the scope of this PR is to broad, I'm happy to split this into one PR adding the WithAttrs functionality and another one using it in the otlp/otlphttp exporters

bogdandrutu · 2026-03-24T16:16:54Z

 		exporterhelper.WithQueue(oCfg.QueueConfig),
 		exporterhelper.WithStart(oce.start),
 		exporterhelper.WithShutdown(oce.shutdown),
+		exporterhelper.WithAttrs(attribute.String("endpoint", oCfg.ClientConfig.Endpoint)),


Is this the semantic convention for it?

I considered both server/destination.address but since they don't include the path, they're not a good fit.

url.full would work but IMHO this doesn't clearly communicate that the value is the remote endpoint

I think we should define something in the semantic conventions before including it here.

I can do that, which broader scope would be appropriate here? I was thinking maybe otel.component.endpoint (next to otel.component.name/otel.component.type)

Alternatively, extending the server/destination attributes with .path is reasonable as well.

Updated the PR to use server.address + url.path as recommended by @lmolkova in slack

codecov · 2026-04-01T18:04:50Z

Codecov Report

❌ Patch coverage is 98.24561% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 91.31%. Comparing base (5f78c13) to head (8689a0c).
⚠️ Report is 18 commits behind head on main.

Files with missing lines	Patch %	Lines
exporter/otlphttpexporter/factory.go	97.14%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #14998      +/-   ##
==========================================
+ Coverage   91.29%   91.31%   +0.02%     
==========================================
  Files         699      699              
  Lines       44940    44979      +39     
==========================================
+ Hits        41028    41073      +45     
+ Misses       2765     2761       -4     
+ Partials     1147     1145       -2

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

codspeed-hq · 2026-04-09T12:32:23Z

Merging this PR will not alter performance

⚠️

Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

✅ 7 untouched benchmarks
⏩ 76 skipped benchmarks¹

_{Comparing theSuess:push-lstslmkuuvvy (8689a0c) with main (5f78c13)}

76 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

theSuess · 2026-04-13T13:49:27Z

@dmathieu I've rebased on the latest main & the merge freeze should be over, can you allow the CI to run & merge if everything is good from your side?

evan-bradley · 2026-04-14T20:18:17Z

@theSuess Could you describe in a little more depth what's currently missing? We instrument the clients for the OTLP exporters with the Go SDK gRPC/HTTP instrumentations. I just verified I see the server.address attribute on data points on the http.client.request.duration metric reported from the OTLP/HTTP exporter.

If possible, I think those instrumentations would be the best place to put anything that should be there, but I may be missing something.

theSuess · 2026-04-15T05:57:35Z

@evan-bradley the http.client.* metrics do indeed have the same information, however these don't represent the same data. If I want to find out how many log records/metrics points/spans I'm sending to a specific endpoint, the number of http requests will probably be lower due to batching.

Another downside of this set of metrics is that they don't split by exporter so it's not possible to figure out which exporter is sending to which endpoint without parsing the config

evan-bradley · 2026-04-15T17:07:42Z

Got it, thanks for the explanation. I think I got a bit spun around by the attributes being added, I see why this makes sense.

evan-bradley

Makes sense to me. Checked the attributes against the HTTP/RPC semconvs and the Slack conversation and they make sense to me.

(There could be an argument for including http.request.method to align with the http.request.* metrics, but it will generally be POST, so maybe there's no benefit)

evan-bradley

Nit comment about the changelog entry, but looks good to me. Thanks.

otelbot · 2026-04-22T09:46:43Z

Thank you for your contribution @theSuess! 🎉 We would like to hear from you about your experience contributing to OpenTelemetry by taking a few minutes to fill out this survey.

…ocessortest to v0.151.0 (#65) This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [go.opentelemetry.io/collector/processor/processortest](https://github.com/open-telemetry/opentelemetry-collector) | `v0.150.0` → `v0.151.0` | ![age](https://developer.mend.io/api/mc/badges/age/go/go.opentelemetry.io%2fcollector%2fprocessor%2fprocessortest/v0.151.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/go/go.opentelemetry.io%2fcollector%2fprocessor%2fprocessortest/v0.150.0/v0.151.0?slim=true) | --- ### Release Notes <details> <summary>open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector/processor/processortest)</summary> ### [`v0.151.0`](https://github.com/open-telemetry/opentelemetry-collector/blob/HEAD/CHANGELOG.md#v1570v01510) [Compare Source](open-telemetry/opentelemetry-collector@v0.150.0...v0.151.0) ##### 🛑 Breaking changes 🛑 - `cmd/builder`: In the generated Collector source, the `replace` statements in the Go module will now use relative paths by default. ([#15097](open-telemetry/opentelemetry-collector#15097)) We expect that this will not break existing use-cases where the generated collector is only used in an interim manner for builds. It enables the possibility of tracking the generated Collector code as a longer living artifact, allowing it to be run on any machine (whereas absolute paths will be different depending on the machine the Collector source is generated on.) We have added `dist::use_absolute_replace_paths` to go back to the absolute path behaviour in the case where there is an unforeseen use-case that requires absolute paths. - `pkg/confighttp`: Stabilize framedSnappy feature gate. ([#15096](open-telemetry/opentelemetry-collector#15096)) ##### 💡 Enhancements 💡 - `all`: Add declarative schema support for service telemetry resource configuration. ([#14411](open-telemetry/opentelemetry-collector#14411)) The `service::telemetry::resource` configuration now accepts the declarative schema with explicit name/value pairs: ```yaml service: telemetry: resource: schema_url: https://opentelemetry.io/schemas/1.38.0 attributes: - name: service.name value: my-collector - name: host.name value: collector-host ``` The legacy inline attribute map format is still supported for backward compatibility: ```yaml service: telemetry: resource: service.name: my-collector host.name: collector-host ``` Note: `resource.detectors` is accepted for forward compatibility but is not yet applied by the collector. - `exporter/otlp_grpc`: Added the `server.address` and `url.path` attributes to metrics generated by the otlp exporter. ([#14998](open-telemetry/opentelemetry-collector#14998)) - `exporter/otlp_http`: Added the `server.address` and `url.path` attributes to metrics generated by the otlp\_http exporter. ([#14998](open-telemetry/opentelemetry-collector#14998)) - `pkg/config/configgrpc`: Add `UserAgent` field to `ClientConfig` to allow overriding the default gRPC user-agent string. ([#14686](open-telemetry/opentelemetry-collector#14686)) The otlp gRPC exporter was unconditionally setting the User-Agent via grpc.WithUserAgent() at dial time, which takes precedence over per-call metadata, causing any user-configured User-Agent to be silently discarded. A dedicated `UserAgent` field has been added to `ClientConfig` which, when set, is used in the dial option directly instead of the default BuildInfo-derived string. - `pkg/config/configgrpc`: Accept gRPC resolver scheme URIs in client endpoint (e.g. passthrough:///host:port) to allow control over name resolution ([#14990](open-telemetry/opentelemetry-collector#14990)) After the migration to grpc.NewClient, some gRPC client components such as the OTLP exporter experienced connection issues in dual-stack DNS environments. This can now be fixed by using the passthrough:/// gRPC resolver scheme in the endpoint field. - `pkg/config/confignet`: Add support for Windows Named Pipe (npipe) transport ([#15085](open-telemetry/opentelemetry-collector#15085)) - `pkg/service`: Emit a warning when using the old v0.2.0 declarative config format ([#15088](open-telemetry/opentelemetry-collector#15088)) ##### 🧰 Bug fixes 🧰 - `pkg/otelcol`: Print components exactly once in the `otelcol components` command ([#14682](open-telemetry/opentelemetry-collector#14682)) This resolves an issue where aliased components were skipped. - `pkg/otelcol`: Synchronize Collector Run and Shutdown lifecycles so that Shutdown blocks until Run completes all cleanup. ([#4947](open-telemetry/opentelemetry-collector#4947)) Shutdown now blocks until Run finishes cleanup, matching http.Server semantics. If Shutdown is called before Run, the next Run call returns nil after cleaning up the config provider. - `pkg/pdata`: Use spec-compliant string representation for NaN, Infinity, and -Infinity in Value.AsString(). ([#14487](open-telemetry/opentelemetry-collector#14487)) - `pkg/pprofile`: Fix data corruption of resource and scope attributes after marshal-unmarshal-merge round-trip. ([#15084](open-telemetry/opentelemetry-collector#15084)) - `pkg/service`: Non-string resource attributes in telemetry configuration now return an error instead of panicking ([#15171](open-telemetry/opentelemetry-collector#15171)) - `pkg/xscraperhelper`: fix the merge of profiles in the profiling scraper helpers ([#14790](open-telemetry/opentelemetry-collector#14790)) - `receiver/otlp`: Fix profiles receiver reporting its samples as spans ([#15089](open-telemetry/opentelemetry-collector#15089))  </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).  Reviewed-on: https://gitea.t000-n.de/t.behrendt/tracebasedlogsampler/pulls/65 Reviewed-by: t.behrendt <[email protected]> Co-authored-by: Renovate Bot <[email protected]> Co-committed-by: Renovate Bot <[email protected]>

…1.58.0 (#60) This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [go.opentelemetry.io/collector/confmap](https://github.com/open-telemetry/opentelemetry-collector) | `v1.56.0` → `v1.58.0` | ![age](https://developer.mend.io/api/mc/badges/age/go/go.opentelemetry.io%2fcollector%2fconfmap/v1.58.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/go/go.opentelemetry.io%2fcollector%2fconfmap/v1.56.0/v1.58.0?slim=true) | --- ### Release Notes <details> <summary>open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector/confmap)</summary> ### [`v1.58.0`](https://github.com/open-telemetry/opentelemetry-collector/blob/HEAD/CHANGELOG.md#v1580v01520) ##### 💡 Enhancements 💡 - `pkg/exporterhelper`: Add `otelcol_exporter_in_flight_requests` metric to track the number of export requests currently in-flight per exporter. ([#15009](open-telemetry/opentelemetry-collector#15009)) This UpDownCounter increments in startOp and decrements in endOp, allowing operators to monitor concurrent export activity and detect when an exporter is saturating its worker pool. ##### 🧰 Bug fixes 🧰 - `pkg/confighttp`: Close the original request body after reading block-format `Content-Encoding: snappy` requests. ([#15262](open-telemetry/opentelemetry-collector#15262)) - `pkg/confighttp`: Recover from panics in decompression libraries, return HTTP 400 instead of 500. ([#13228](open-telemetry/opentelemetry-collector#13228)) - `pkg/confighttp`: Enforce `max_request_body_size` on `Content-Encoding: snappy` requests before the decoded buffer is allocated. ([#15252](open-telemetry/opentelemetry-collector#15252)) - `pkg/otelcol`: Stop emitting verbose gRPC transport messages at WARN during normal client disconnect. ([#5169](open-telemetry/opentelemetry-collector#5169)) grpc-go gates chatty per-RPC notices (e.g. "HandleStreams failed to read frame: connection reset by peer") behind `LoggerV2.V(2)`. zapgrpc.Logger.V conflates grpclog verbosity with zap severity, so V(2) returns true whenever WARN is enabled and these messages emit at WARN. Wrap the installed grpclog.LoggerV2 with a corrected V() that compares against a fixed verbosity threshold, matching grpclog's intended semantics. See [uber-go/zap#1544](uber-go/zap#1544). - `pkg/pdata`: `pcommon.Value.AsString` no longer HTML-escapes `<`, `>`, and `&` inside `ValueTypeMap` and `ValueTypeSlice` values, matching the behavior already used for `ValueTypeStr`. ([#14662](open-telemetry/opentelemetry-collector#14662)) - `pkg/service`: Fix Prometheus config defaults mismatch when host is explicitly set in telemetry configuration. ([#13867](open-telemetry/opentelemetry-collector#13867)) When users explicitly configured the telemetry metrics section (e.g. to change the host), the Prometheus exporter boolean fields (WithoutScopeInfo, WithoutUnits, WithoutTypeSuffix) defaulted to nil/false instead of true, causing metric name format changes compared to the implicit default configuration. This fix applies the correct defaults during config unmarshaling. - `pkg/service`: Return noop tracer provider when no trace processors are defined ([#15135](open-telemetry/opentelemetry-collector#15135))  ### [`v1.57.0`](https://github.com/open-telemetry/opentelemetry-collector/blob/HEAD/CHANGELOG.md#v1570v01510) ##### 🛑 Breaking changes 🛑 - `cmd/builder`: In the generated Collector source, the `replace` statements in the Go module will now use relative paths by default. ([#15097](open-telemetry/opentelemetry-collector#15097)) We expect that this will not break existing use-cases where the generated collector is only used in an interim manner for builds. It enables the possibility of tracking the generated Collector code as a longer living artifact, allowing it to be run on any machine (whereas absolute paths will be different depending on the machine the Collector source is generated on.) We have added `dist::use_absolute_replace_paths` to go back to the absolute path behaviour in the case where there is an unforeseen use-case that requires absolute paths. - `pkg/confighttp`: Stabilize framedSnappy feature gate. ([#15096](open-telemetry/opentelemetry-collector#15096)) ##### 💡 Enhancements 💡 - `all`: Add declarative schema support for service telemetry resource configuration. ([#14411](open-telemetry/opentelemetry-collector#14411)) The `service::telemetry::resource` configuration now accepts the declarative schema with explicit name/value pairs: ```yaml service: telemetry: resource: schema_url: https://opentelemetry.io/schemas/1.38.0 attributes: - name: service.name value: my-collector - name: host.name value: collector-host ``` The legacy inline attribute map format is still supported for backward compatibility: ```yaml service: telemetry: resource: service.name: my-collector host.name: collector-host ``` Note: `resource.detectors` is accepted for forward compatibility but is not yet applied by the collector. - `exporter/otlp_grpc`: Added the `server.address` and `url.path` attributes to metrics generated by the otlp exporter. ([#14998](open-telemetry/opentelemetry-collector#14998)) - `exporter/otlp_http`: Added the `server.address` and `url.path` attributes to metrics generated by the otlp\_http exporter. ([#14998](open-telemetry/opentelemetry-collector#14998)) - `pkg/config/configgrpc`: Add `UserAgent` field to `ClientConfig` to allow overriding the default gRPC user-agent string. ([#14686](open-telemetry/opentelemetry-collector#14686)) The otlp gRPC exporter was unconditionally setting the User-Agent via grpc.WithUserAgent() at dial time, which takes precedence over per-call metadata, causing any user-configured User-Agent to be silently discarded. A dedicated `UserAgent` field has been added to `ClientConfig` which, when set, is used in the dial option directly instead of the default BuildInfo-derived string. - `pkg/config/configgrpc`: Accept gRPC resolver scheme URIs in client endpoint (e.g. passthrough:///host:port) to allow control over name resolution ([#14990](open-telemetry/opentelemetry-collector#14990)) After the migration to grpc.NewClient, some gRPC client components such as the OTLP exporter experienced connection issues in dual-stack DNS environments. This can now be fixed by using the passthrough:/// gRPC resolver scheme in the endpoint field. - `pkg/config/confignet`: Add support for Windows Named Pipe (npipe) transport ([#15085](open-telemetry/opentelemetry-collector#15085)) - `pkg/service`: Emit a warning when using the old v0.2.0 declarative config format ([#15088](open-telemetry/opentelemetry-collector#15088)) ##### 🧰 Bug fixes 🧰 - `pkg/otelcol`: Print components exactly once in the `otelcol components` command ([#14682](open-telemetry/opentelemetry-collector#14682)) This resolves an issue where aliased components were skipped. - `pkg/otelcol`: Synchronize Collector Run and Shutdown lifecycles so that Shutdown blocks until Run completes all cleanup. ([#4947](open-telemetry/opentelemetry-collector#4947)) Shutdown now blocks until Run finishes cleanup, matching http.Server semantics. If Shutdown is called before Run, the next Run call returns nil after cleaning up the config provider. - `pkg/pdata`: Use spec-compliant string representation for NaN, Infinity, and -Infinity in Value.AsString(). ([#14487](open-telemetry/opentelemetry-collector#14487)) - `pkg/pprofile`: Fix data corruption of resource and scope attributes after marshal-unmarshal-merge round-trip. ([#15084](open-telemetry/opentelemetry-collector#15084)) - `pkg/service`: Non-string resource attributes in telemetry configuration now return an error instead of panicking ([#15171](open-telemetry/opentelemetry-collector#15171)) - `pkg/xscraperhelper`: fix the merge of profiles in the profiling scraper helpers ([#14790](open-telemetry/opentelemetry-collector#14790)) - `receiver/otlp`: Fix profiles receiver reporting its samples as spans ([#15089](open-telemetry/opentelemetry-collector#15089))  </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).  Reviewed-on: https://gitea.t000-n.de/t.behrendt/tracebasedlogsampler/pulls/60 Reviewed-by: t.behrendt <[email protected]> Co-authored-by: Renovate Bot <[email protected]> Co-committed-by: Renovate Bot <[email protected]>

theSuess force-pushed the push-lstslmkuuvvy branch from f78e5b8 to abaa2ca Compare March 24, 2026 10:44

theSuess marked this pull request as ready for review March 24, 2026 10:45

theSuess requested review from a team, bogdandrutu and dmitryax as code owners March 24, 2026 10:45

theSuess changed the title ~~feat: add endpoint attribute to otlp exporter~~ Add endpoint attribute to otlp exporter Mar 24, 2026

bogdandrutu reviewed Mar 24, 2026

View reviewed changes

theSuess force-pushed the push-lstslmkuuvvy branch from abaa2ca to 859e181 Compare March 25, 2026 09:33

theSuess mentioned this pull request Mar 26, 2026

feat: opentelemetry-collector-observ-lib grafana/jsonnet-libs#1610

Merged

theSuess force-pushed the push-lstslmkuuvvy branch from 859e181 to d6dfcb8 Compare April 1, 2026 10:20

theSuess requested a review from bogdandrutu April 1, 2026 10:22

theSuess force-pushed the push-lstslmkuuvvy branch 5 times, most recently from ee9f6d8 to 8abb683 Compare April 9, 2026 11:43

dmathieu reviewed Apr 9, 2026

View reviewed changes

Comment thread exporter/otlpexporter/factory.go

theSuess force-pushed the push-lstslmkuuvvy branch from 8abb683 to a645664 Compare April 10, 2026 07:10

theSuess requested a review from dmathieu April 10, 2026 07:22

dmathieu approved these changes Apr 10, 2026

View reviewed changes

theSuess force-pushed the push-lstslmkuuvvy branch 3 times, most recently from 916d6c7 to 7e3682c Compare April 13, 2026 13:48

dmathieu added the ready-to-merge Code review completed; ready to merge by maintainers label Apr 13, 2026

theSuess force-pushed the push-lstslmkuuvvy branch 2 times, most recently from 85e56f2 to 0eb460c Compare April 14, 2026 12:19

evan-bradley removed the ready-to-merge Code review completed; ready to merge by maintainers label Apr 14, 2026

evan-bradley approved these changes Apr 15, 2026

View reviewed changes

Comment thread .chloggen/add-endpoint-to-otlpexporter-metrics.yaml

theSuess force-pushed the push-lstslmkuuvvy branch from 0eb460c to 89c8104 Compare April 16, 2026 13:43

theSuess requested a review from evan-bradley April 16, 2026 13:44

evan-bradley approved these changes Apr 20, 2026

View reviewed changes

Comment thread .chloggen/add-endpoint-to-otlphttpexporter-metrics.yaml Outdated

evan-bradley added the ready-to-merge Code review completed; ready to merge by maintainers label Apr 20, 2026

feat: add endpoint attribute to otlp exporter

8689a0c

theSuess force-pushed the push-lstslmkuuvvy branch from 89c8104 to 8689a0c Compare April 21, 2026 08:57

theSuess requested a review from evan-bradley April 21, 2026 08:57

evan-bradley approved these changes Apr 21, 2026

View reviewed changes

mx-psi added this pull request to the merge queue Apr 22, 2026

Merged via the queue into open-telemetry:main with commit b308996 Apr 22, 2026
65 checks passed

jkoronaAtCisco mentioned this pull request Apr 30, 2026

Update OpenTelemetry Dependencies to latest signalfx/splunk-otel-collector#7509

Merged

Uh oh!

Conversation

theSuess commented Mar 24, 2026

Description

Testing

Documentation

Uh oh!

theSuess commented Mar 24, 2026

Uh oh!

bogdandrutu Mar 24, 2026

Choose a reason for hiding this comment

Uh oh!

theSuess Mar 25, 2026

Choose a reason for hiding this comment

Uh oh!

iblancasa Mar 25, 2026

Choose a reason for hiding this comment

Uh oh!

theSuess Mar 26, 2026

Choose a reason for hiding this comment

Uh oh!

theSuess Apr 1, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

codecov Bot commented Apr 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

codspeed-hq Bot commented Apr 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Merging this PR will not alter performance

Footnotes

Uh oh!

Uh oh!

theSuess commented Apr 13, 2026

Uh oh!

evan-bradley commented Apr 14, 2026

Uh oh!

theSuess commented Apr 15, 2026

Uh oh!

evan-bradley commented Apr 15, 2026

Uh oh!

evan-bradley left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

evan-bradley left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

otelbot Bot commented Apr 22, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

codecov Bot commented Apr 1, 2026 •

edited

Loading

codspeed-hq Bot commented Apr 9, 2026 •

edited

Loading