Update All OpenTelemetry Collector packages - #107
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
File name: pkg/splunkinputsreceiver/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
File name: pkg/splunkoutputsexporter/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
Bot
force-pushed
the
renovate/all-opentelemetry-collector-packages
branch
2 times, most recently
from
August 12, 2026 12:10
a7c818c to
55d8960
Compare
renovate
Bot
force-pushed
the
renovate/all-opentelemetry-collector-packages
branch
3 times, most recently
from
August 19, 2026 17:27
9c6a87e to
94749fa
Compare
renovate
Bot
force-pushed
the
renovate/all-opentelemetry-collector-packages
branch
from
August 20, 2026 07:17
94749fa to
ec3a161
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.63.0→v1.65.0v0.157.0→v0.159.0v1.63.0→v1.65.0v1.63.0→v1.65.0v1.63.0→v1.65.0v1.63.0→v1.65.0v0.157.0→v0.159.0v1.63.0→v1.65.0v0.157.0→v0.159.0v0.157.0→v0.159.0v1.63.0→v1.65.0v1.63.0→v1.65.0v1.63.0→v1.65.0v0.157.0→v0.159.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/component)
v1.65.0💡 Enhancements 💡
pkg/exporterhelper: Add thepkg.exporterhelper.queueBatchEnabledfeature gate (#14038, #13582, #12022)When enabled, the batch settings returned by
NewDefaultQueueConfig()havebatch::enabledtrue. See migration RFC.🧰 Bug fixes 🧰
pkg/exporterhelper: Recordotelcol_exporter_queue_batch_send_sizeandotelcol_exporter_queue_batch_send_size_bytesafter batching, and addotelcol_exporter_enqueue_sizeandotelcol_exporter_enqueue_size_bytesfor enqueue-time sizes. (#14674)Previously the batch send size histograms were recorded at enqueue time (
Offer), so theymeasured incoming request sizes rather than the post-batching request handed to the
downstream sender. Those histograms are now recorded in the obs report sender.
The previous enqueue-time measurements are preserved under the new
otelcol_exporter_enqueue_sizeandotelcol_exporter_enqueue_size_bytesmetrics forqueue sizing. Users with the exporter batcher enabled will observe different values for
otelcol_exporter_queue_batch_send_size*.otelcol_exporter_queue_batch_send_sizeandotelcol_exporter_queue_batch_send_size_bytesare now only recorded when
sending_queue::batchis configured; they will not appear at allfor exporters that do not enable batching.
pkg/scraperhelper: Use{record}instead of{datapoint}as the unit of the log record and profile record scraper metrics (#15730)Affects
otelcol_scraper_scraped_log_records,otelcol_scraper_errored_log_records,otelcol_scraper_scraped_profile_recordsandotelcol_scraper_errored_profile_records.v1.64.0🚀 New components 🚀
processor/queuebatch: Newqueuebatchprocessorto replace the legacybatchprocessor. (#15047, #13582, #12022, #11308, #8272, #6046)New implementation is based exporterhelper, uses same configuration as
sending_queue.💡 Enhancements 💡
cmd/mdatagen: Add first-class extended type aliases (int64, duration, opaque_string, id, opaque_map, etc.) to config schemas in metadata.yaml (#15513)Authors can now write
type: int64,type: duration,type: opaque_string,type: id, ortype: opaque_mapdirectly as a property type in theconfig:section ofmetadata.yaml.Each alias expands to the correct JSON Schema representation and Go type automatically.
Existing uses of standard JSON Schema types,
format:, andx-customType:remain supportedwithout migration.
extension/memory_limiter: Promote the memory limiter extension to beta stability. (#14533)🧰 Bug fixes 🧰
cmd/mdatagen: Removes the extra line in the documentation.md around description (#15664)cmd/mdatagen: Auto-enable v1 metrics when legacy metric is enabled and v1 feature gate is on (#15650)When the v1 feature gate is enabled and a legacy metric is enabled, the corresponding
v1 metric is now programmatically enabled so users don't need to add the v1 metric
to their config.
cmd/mdatagen: Fix incorrect collision warning for versioned metrics with different emitted names (#15648)Same name collision detection (type/attribute checks) was being used for versioned metrics
with different names. This caused the legacy metric to be disabled which was incorrect and also
a warning msg was being incorrectly logged that stated the metrics had the same name when in
fact they had different names.
cmd/mdatagen: Versioned metrics don't handle renamed attributes with same type (#15595)Versioned metrics need to support emitting legacy and latest attributes when the metric name is the same but the
attributes names differ. This was not working when the attributes name changed but the type remained the same.
Here we add support to versioned metrics with renamed attributes where those attributes have the same type.
exporter/debug: Fix profile sample attribute formatting for non-string values (#15647)Previously, non-string values produced malformed output such as
%!s(int64=42).Profile sample attributes now use the debug exporter's typed attribute format, such as
Int(42).This will also change strings from
hello-worldtoStr(hello-world).pkg/config/configtls: Fix goroutine and file descriptor leak whenclient_ca_file_reloadis enabled (#9221)Every call to
ServerConfig.LoadTLSConfigwithclient_ca_file_reloadenabled started afile watcher goroutine that could never be stopped, since the reloader was not reachable
from the returned
*tls.Config. The client CA file is now checked for changes while TLShandshakes are served, at most once per second, matching how
reload_intervalalreadyreloads the server certificate. No background goroutine is started, so nothing is left
behind when a server is torn down and recreated.
Configuration
📅 Schedule: (UTC)
🚦 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.