Update All OpenTelemetry Collector packages #183
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.21.0->v1.44.0v0.115.0->v0.138.0v0.115.0->v0.138.0v0.115.0->v0.120.0v0.115.0->v0.138.0v0.115.0->v0.138.0v0.115.0->v0.136.0v1.21.0->v1.44.0v0.115.0->v0.138.0v0.115.0->v0.138.0v1.21.0->v1.44.0v1.21.0->v1.44.0v1.21.0->v1.44.0v0.115.0->v0.138.0v1.21.0->v1.44.0v1.21.0->v1.44.0v1.21.0->v1.44.0v1.21.0->v1.44.0v0.115.0->v0.138.0v0.115.0->v0.138.0v1.21.0->v1.44.0v0.115.0->v0.138.0v0.115.0->v0.116.0v0.115.0->v0.138.0v0.115.0->v0.135.0v0.115.0->v0.138.0v0.115.0->v0.138.0v0.115.0->v0.138.0v0.115.0->v0.138.0v0.115.0->v0.120.0v0.115.0->v0.121.0v0.115.0->v0.121.0v0.115.0->v0.117.0v0.115.0->v0.138.0v0.115.0->v0.138.0v0.115.0->v0.138.0v1.21.0->v1.44.0v0.115.0->v0.138.0v0.115.0->v0.138.0v0.115.0->v0.138.0v1.21.0->v1.44.0v0.115.0->v0.138.0v0.115.0->v0.138.0v0.115.0->v0.131.0v0.115.0->v0.116.0v0.115.0->v0.122.1v0.115.0->v0.138.0v0.115.0->v0.138.0v0.115.0->v0.116.0v0.115.0->v0.116.0v0.115.0->v0.138.0v0.115.0->v0.121.0v0.115.0->v0.138.0v0.115.0->v0.116.0v0.115.0->v0.138.0v0.115.0->v0.138.0v0.115.0->v0.128.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.44.0🛑 Breaking changes 🛑
all: Remove deprecated typeTracesConfig(#14036)pkg/exporterhelper: Add default values forsending_queue::batchconfiguration. (#13766)Setting
sending_queue::batchto an empty value now results in the same setup as the default batch processor configuration.all: Add unified print-config command with mode support (redacted, unredacted), json support (unstable), and validation support. (#11775)This replaces the
print-initial-configcommand. See theservicepackage README for more details. The original command nameprint-initial-configremains an alias, to be retired with the feature flag.💡 Enhancements 💡
all: Addkeep_alives_enabledoption to ServerConfig to control HTTP keep-alives for all components that create an HTTP server. (#13783)pkg/otelcol: Avoid unnecessary mutex in collector logs, replace by atomic pointer (#14008)cmd/mdatagen: Add lint/ordering validation for metadata.yaml (#13781)pdata/xpdata: Refactor JSON marshaling and unmarshaling to usepcommon.Valueinstead ofAnyValue. (#13837)pkg/exporterhelper: ExposeMergeCtxin exporterhelper's queue batch settings` (#13742)🧰 Bug fixes 🧰
all: Fix zstd decoder data corruption due to decoder pooling for all components that create an HTTP server. (#13954)pkg/otelcol: Remove UB when taking internal logs and move them to the final zapcore.Core (#14009)This can happen because of a race on accessing
logsTaken.pkg/confmap: Fix a potential race condition in confmap by closing the providers first. (#14018)v1.43.0💡 Enhancements 💡
cmd/mdatagen: Improve validation for resource attributeenabledfield in metadata files (#12722)Resource attributes now require an explicit
enabledfield in metadata.yaml files, while regular attributesare prohibited from having this field. This improves validation and prevents configuration errors.
all: Changelog entries will now have their component field checked against a list of valid components. (#13924)This will ensure a more standardized changelog format which makes it easier to parse.
pkg/pdata: Mark featuregate pdata.useCustomProtoEncoding as stable (#13883)v1.42.0💡 Enhancements 💡
xpdata: Add Serialization and Deserialization of AnyValue (#12826)debugexporter: add support for batching (#13791)The default queue size is 1
configtls: Add early validation for TLS server configurations to fail fast when certificates are missing instead of failing at runtime. (#13130, #13245)mdatagen: Expose stability level in generated metric documentation (#13748)internal/tools: Add support for modernize in Makefile (#13796)🧰 Bug fixes 🧰
otelcol: Fix a potential deadlock during collector shutdown. (#13740)otlpexporter: fix the validation of unix socket endpoints (#13826)v1.41.0💡 Enhancements 💡
exporterhelper: Add newexporter_queue_batch_send_sizeandexporter_queue_batch_send_size_bytesmetrics, showing the size of telemetry batches from the exporter. (#12894)v1.40.0💡 Enhancements 💡
pdata: Add custom grpc/encoding that replaces proto and calls into the custom marshal/unmarshal logic in pdata. (#13631)This change should not affect other gRPC calls since it fallbacks to the default grpc/proto encoding if requests are not pdata/otlp requests.
pdata: Avoid copying the pcommon.Map when same origin (#13731)This is a very large improvement if using OTTL with map functions since it will avoid a map copy.
exporterhelper: Respectnum_consumerswhen batching and partitioning are enabled. (#13607)🧰 Bug fixes 🧰
pdata: Correctly parse OTLP payloads containing non-packed repeated primitive fields (#13727, #13730)This bug prevented the Collector from ingesting most Histogram, ExponentialHistogram,
and Profile payloads.
v1.39.0🛑 Breaking changes 🛑
all: Increase minimum Go version to 1.24 (#13627)💡 Enhancements 💡
otlphttpexporter: Addprofiles_endpointconfiguration option to allow custom endpoint for profiles data export (#13504)The
profiles_endpointconfiguration follows the same pattern astraces_endpoint,metrics_endpoint, andlogs_endpoint.When specified, profiles data will be sent to the custom URL instead of the default
{endpoint}/v1development/profiles.pdata: Add support for local memory pooling for data objects. (#13678)This is still an early experimental (alpha) feature. Do not recommended to be used production. To enable use "--featuregate=+pdata.useProtoPooling"
pdata: Optimize CopyTo messages to avoid any copy when same source and destination (#13680)receiverhelper: New feature flag to make receiverhelper distinguish internal vs. downstream errors using newotelcol_receiver_failed_xandotelcol_receiver_requestsmetrics (#12207, #12802)This is a breaking change for the semantics of the otelcol_receiver_refused_metric_points, otelcol_receiver_refused_log_records and otelcol_receiver_refused_spans metrics.
These new metrics and semantics are enabled through the
receiverhelper.newReceiverMetricsfeature gate.debugexporter: Add support for entity references in debug exporter output (#13324)pdata: Fix unnecessary allocation of a new state when adding new values to pcommon.Map (#13634)service: Implement refcounting for pipeline data owned memory. (#13631)This feature is protected by
--featuregate=+pdata.useProtoPooling.service: Add a debug-level log message when a consumer returns an error. (#13357)xpdata: Optimize xpdata/context for persistent queue when only one value for key (#13636)otlpreceiver: Log the listening addresses of the receiver, rather than the configured endpoints. (#13654)pdata: Use the newly added proto marshaler/unmarshaler for the official proto Marshaler/Unmarshaler (#13637)If any problems observed with this consider to disable the featuregate
--feature-gates=-pdata.useCustomProtoEncodingconfigtls: Enable X25519MLKEM768 as per draft-ietf-tls-ecdhe-mlkem (#13670)🧰 Bug fixes 🧰
exporterhelper: Prevent uncontrolled goroutines in batcher due to a incorrect worker pool behaviour. (#13689)service: Ensure the insecure configuration is accounted for when normalizing the endpoint. (#13691)configoptional: Allow validating nested types (#13579)configoptional.Optionalnow implementsxconfmap.Validatorbatchprocessor: Fix UB in batch processor when trying to read bytes size after adding request to pipeline (#13698)This bug only happens id detailed metrics are enabled and also an async (sending queue enabled) exporter that mutates data is configure.
v1.38.0🛑 Breaking changes 🛑
componentstatus: Change the signature of the componentstatus.NewEvent to accept multiple options. (#13210)Changes the signature of the component.NewEvent to accept multiple EventBuilderOption,
like the new WithAttributes constructor.
🚩 Deprecations 🚩
service: move service.noopTraceProvider feature gate to deprecated stage (#13492)The functionality of the feature gate is available via configuration with the following telemetry settings:
mdatagen: Remove the deletion ofgenerated_component_telemetry_test.go. (#12067)This file used to be generated by mdatagen. Starting with 0.122.0, the code deletes that file.
It is no longer necessary to delete the file, as code has had time to upgrade to mdatagen and delete the file.
service: Thetelemetry.disableHighCardinalityMetricsfeature gate is deprecated (#13537)The feature gate is now deprecated since metric views can be configured.
The feature gate will be removed in v0.134.0.
The metric attributes removed by this feature gate are no longer emitted
by the Collector by default, but if needed, you can achieve the same
functionality by configuring the following metric views:
Note that this requires setting
service::telemetry::metrics::level: detailed.If you have a strong use case for using views in combination with a different
level, please show your interest in
#10769.
💡 Enhancements 💡
pdata: Generate Logs/Traces/Metrics/Profiles and p[log|trace|metric|profile]ExportResponse with pdatagen. (#13597)This change brings consistency on how these structs are written and remove JSON marshaling/unmarshaling hand written logic.
confighttp: Add option to configure ForceAttemptHTTP2 to support HTTP/1 specific transport settings. (#13426)pdata: Avoid unnecessary buffer copy when JSON marshal fails. (#13598)cmd/mdatagen: Use a custom host implementation for lifecycle tests (#13589)Use a custom noop host implementation that implements all non-deprecated, publicly-accessible interfaces implemented by the Collector service.
processorhelper: Add processor internal duration metric. (#13231)pdata: Improve RemoveIf for slices to not reference anymore the removed memory (#13522)🧰 Bug fixes 🧰
pdata: Fix null pointer access when copying into a slice with larger cap but smaller len. (#13523)confighttp: Fix middleware configuration field name from "middleware" to "middlewares" for consistency with configgrpc (#13444)memorylimiterextension, memorylimiterprocessor: Memory limiter extension and processor shutdown don't throw an error if the component was not started first. (#9687)The components would throw an error if they were shut down before being started.
With this change, they will no longer return an error, conforming to the lifecycle of components expected.
confighttp: Reuse zstd Reader objects (#11824)v1.37.0🛑 Breaking changes 🛑
confighttp: Moveconfighttp.framedSnappyfeature gate to beta. (#10584)💡 Enhancements 💡
exporter/debug: Move to alpha stability except profiles (#13487)exporterhelper: Enableexporter.PersistRequestContextfeature gate by default. (#13437)Request context is now preserved by default when using persistent queues.
Note that Auth extensions context is not propagated through the persistent queue.
pdata: Use pdatagen to generate marshalJSON without using gogo proto jsonpb. (#13450)otlpreceiver: Remove usage of gogo proto which uses reflect.Value.MethodByName. Removes one source of disabling DCE. (#12747)exporterhelper: Fix metrics split logic to consider metrics description into the size. (#13418)service: New pipeline instrumentation now differentiates internal failures from downstream errors (#13234)With the telemetry.newPipelineTelemetry feature gate enabled, the "received" and "produced"
metrics related to a component now distinguish between two types of errors:
error coming from a downstream component processing that data.
pdata: Remove usage of text/template from pdata, improves DCE. (#12747)architecture: New Tier 3 platform riscv64 allowing the collector to be built and distributed for this platform. (#13462)🧰 Bug fixes 🧰
exporterhelper: Prevents the exporter for being stuck when telemetry data is bigger than batch.max_size (#12893)mdatagen: Fix import paths for mdatagen component (#13069)otlpreceiver: Error handler correctly fallbacks to content type (#13414)pdata/pprofiles: Fix profiles JSON unmarshal logic for originalPayload. The bytes have to be base64 encoded. (#13483)xpdata: Fix unmarshaling JSON for entities, add e2e tests to avoid this in the future. (#13480)service: Downgrade dependency of prometheus exporter in OTel Go SDK (#13429)This fixes the bug where collector's internal metrics are emitted with an unexpected suffix in their names when users configure the service::telemetry::metrics::readers with Prometheus
service: Revert Default internal metrics config now enablesotel_scope_labels (#12939, #13344)Reverting change temporarily due to prometheus exporter downgrade. This unfortunately re-introduces the bug that instrumentation scope attributes cause errors in Prometheus exporter. See #12939 for details.
builder: Remove undocumented handling ofDIST_*environment variables replacements (#13335)v1.36.1🧰 Bug fixes 🧰
service: Fixes bug where internal metrics are emitted with an unexpected suffix in their names when users configureservice::telemetry::metrics::readerswith Prometheus. (#13449)See more details on open-telemetry/opentelemetry-go#7039
v1.36.0❗ Known Issues ❗
Due to a bug in the prometheus exporter, if you are configuring a prometheus exporter, the collector's internal metrics will be emitted with an unexpected suffix in its name. For example, the metric
otelcol_exporter_sent_spans__spans__totalinstead ofotelcol_exporter_sent_spans_total. The workaround is to manually configurewithout_units: truein your prometheus exporter configIf you are using the collector's default Prometheus exporter for exporting internal metrics you are unaffected.
🛑 Breaking changes 🛑
exporter/otlp: Remove deprecated batcher config from OTLP, use queuebatch (#13339)💡 Enhancements 💡
exporterhelper: Enable items and bytes sizers for persistent queue (#12881)exporterhelper: Refactor persistent storage size backup to always record it. (#12890)exporterhelper: Add support to configure a different Sizer for the batcher than the queue (#13313)yaml: Replacedsigs.k8s.io/yamlwithgo.yaml.in/yamlfor improved support and long-term maintainability. (#13308)🧰 Bug fixes 🧰
exporterhelper: Fix exporter.PersistRequestContext feature gate (#13342)exporterhelper: Preserve all metrics metadata when batch splitting. (#13236)Previously, when large batches of metrics were processed, the splitting logic in
metric_batch.gocouldcause the
namefield of some metrics to disappear. This fix ensures that all metric fields areproperly preserved when
metricRequestobjects are split.service: Default internal metrics config now enablesotel_scope_labels (#12939, #13344)By default, the Collector exports its internal metrics using a Prometheus
exporter from the opentelemetry-go repository. With this change, the Collector
no longer sets "without_scope_info" to true in its configuration.
This means that all exported metrics will have
otel_scope_name,otel_scope_schema_url, andotel_scope_versionlabels corresponding to theinstrumentation scope metadata for that metric.
This notably prevents an error when multiple metrics are only distinguished
by their instrumentation scopes and end up aliased during export.
If this is not desired behavior, a Prometheus exporter can be explicitly
configured with this option enabled.
v1.35.0🛑 Breaking changes 🛑
exporterhelper: Remove deprecated sending_queue::blocking options, use sending_queue::block_on_overflow. (#13211)💡 Enhancements 💡
mdatagen: Taught mdatagen to print thego liststderr output on failures, and to rungo listwhere the metadata file is. (#13205)service: SupporConfiguration
📅 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.