-
Couldn't load subscription status.
- Fork 0
Update All OpenTelemetry Collector packages #34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
a81ecc0 to
bd84dbe
Compare
|
bd84dbe to
a2880a4
Compare
a2880a4 to
34367bd
Compare
|
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
34367bd to
9f63b64
Compare
9f63b64 to
7da23ed
Compare
7da23ed to
eaf2f18
Compare
|
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
|
Closed as inactive. Feel free to reopen if this PR is still being worked on. |
This PR contains the following updates:
v1.21.0->v1.26.0v0.115.0->v0.120.0v0.115.0->v0.120.0v0.115.0->v0.120.0v0.115.0->v0.120.0v0.115.0->v0.120.0v0.115.0->v0.120.0v1.21.0->v1.26.0v0.115.0->v0.120.0v0.115.0->v0.120.0v1.21.0->v1.26.0v1.21.0->v1.26.0v1.21.0->v1.26.0v0.115.0->v0.120.0v1.21.0->v1.26.0v1.21.0->v1.26.0v1.21.0->v1.26.0v1.21.0->v1.26.0v0.115.0->v0.120.0v0.115.0->v0.120.0v1.21.0->v1.26.0v0.115.0->v0.120.0v0.115.0->v0.116.0v0.115.0->v0.120.0v0.115.0->v0.120.0v0.115.0->v0.120.0v0.115.0->v0.120.0v0.115.0->v0.120.0v0.115.0->v0.120.0v0.115.0->v0.120.0v0.115.0->v0.120.0v0.115.0->v0.120.0v0.115.0->v0.117.0v0.115.0->v0.120.0v0.115.0->v0.120.0v0.115.0->v0.120.0v1.21.0->v1.26.0v0.115.0->v0.120.0v0.115.0->v0.120.0v0.115.0->v0.120.0v1.21.0->v1.26.0v0.115.0->v0.120.0v0.115.0->v0.120.0v0.115.0->v0.120.0v0.115.0->v0.116.0v0.115.0->v0.120.0v0.115.0->v0.120.0v0.115.0->v0.120.0v0.115.0->v0.116.0v0.115.0->v0.116.0v0.115.0->v0.120.0v0.115.0->v0.120.0v0.115.0->v0.120.0v0.115.0->v0.116.0v0.115.0->v0.120.0v0.115.0->v0.120.0v0.115.0->v0.120.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector/client)
v1.26.0🛑 Breaking changes 🛑
all: Added support for go1.24, bumped minimum version to 1.23 (#12370)mdatagen: Removing deprecated generated funcs and a few test funcs as well. (#12304)service: Align component logger attributes with those defined in RFC (#12217)See Pipeline Component Telemetry RFC
💡 Enhancements 💡
otlpreceiver: Update stability for logs (#12335)exporterhelper: Implement sync disabled queue used when batching is enabled. (#12245)exporterhelper: Enable the new pull-based batcher in exporterhelper (#12291)exporterhelper: Update queue size after the element is done exported (#12399)After this change the active queue size will include elements in the process of being exported.
otelcol: Add featuregate command to display information about available features (#11998)The featuregate command allows users to view detailed information about feature gates
including their status, stage, and description.
🧰 Bug fixes 🧰
memorylimiter: Logger no longer attributes to single signal, pipeline, or component. (#12217)otlpreceiver: Logger no longer attributes to random signal when receiving multiple signals. (#12217)exporterhelper: Fix undefined behavior access to request after send to next component. This causes random memory access. (#12281)exporterhelper: Fix default batcher to correctly call all done callbacks exactly once (#12247)otlpreceiver: Fix OTLP http receiver to correctly set Retry-After (#12367)otlphttpexporter: Fix parsing logic for Retry-After in OTLP http protocol. (#12366)The value of Retry-After field can be either an HTTP-date or delay-seconds and the current logic only parsed delay-seconds.
cmd/builder: Ensure unique aliases for modules with same suffix (#12201)v1.25.0🛑 Breaking changes 🛑
exporterhelper: Rename exporter span signal specific attributes (e.g. "sent_spans" / "send_failed_span") to "items.sent" / "items.failed". (#12165)cmd/mdatagen: Remove dead fieldtelemetry::level(#12144)exporterhelper: Change exporter ID to be a Span level attribute instead on each event. (#12164)This does not have an impact on the level of information emitted, but on the structure of the Span.
cmd/mdatagen: Removelevelfield from metrics definition (#12145)This mechanism will be added back once a new views mechanism is implemented.
service: Value for telemetry exporterotlp.protocolupdated fromgrpc/protobuftogrpc. (#12337)service: internal metrics exported over Prometheus may differ from previous versions. (#11611)Users who do not customize the Prometheus reader should not be impacted. The change to update the internal telemetry to use otel-go config can cause unexpected behaviour
for end users. This change is caused by the default values in
configbeing different from what the Collector has used in previous versions. Thefollowing changes can occur when users configure their
service::telemetry::metrics::readers:_totalsuffix ifwithout_type_suffixis not configured. Setwithout_type_suffixtotrueto disable this.without_unitsis not configured. Setwithout_unitstotrueto disable this.target_infometric will be emitted ifwithout_scope_infois not configured. Setwithout_scope_infoConfiguration
📅 Schedule: Branch creation - "on tuesday" (UTC), 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.