chore(deps): update otelcol #553
Open
+43
−43
Conversation
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
![elastic-renovate-prod[bot]](https://avatars.githubusercontent.com/in/937301?s=60&v=4){kind=small}
|
#552 should take care of this |
elastic-renovate-prod
bot
force-pushed
the
renovate/otelcol
branch
2 times, most recently
from
65cc29a to
ac52602
Compare
elastic-renovate-prod
bot
force-pushed
the
renovate/otelcol
branch
from
ac52602 to
c41002a
Compare
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:
8.18.0->8.18.1v0.2.1->v0.3.0v0.14.0->v0.15.0v0.4.2->v0.6.0v0.5.1->v0.6.0v0.0.0->v0.1.0v0.124.1->v0.125.0v0.124.1->v0.125.0v0.124.1->v0.125.0v0.124.1->v0.125.0v0.124.1->v0.125.0v0.124.1->v0.125.0v0.124.1->v0.125.0v0.124.1->v0.125.0v0.124.1->v0.125.0v0.124.1->v0.125.0v0.124.1->v0.125.0v0.124.1->v0.125.0v0.124.1->v0.125.0v0.124.1->v0.125.0v0.124.1->v0.125.0v0.124.1->v0.125.0v0.124.1->v0.125.0v0.124.1->v0.125.0v0.124.1->v0.125.0v0.124.1->v0.125.0v0.124.1->v0.125.0v0.124.1->v0.125.0v1.30.0->v1.31.0v1.30.0->v1.31.0v1.30.0->v1.31.0v1.30.0->v1.31.0v1.30.0->v1.31.0v0.124.0->v0.125.0v0.124.0->v0.125.0v0.124.0->v0.125.0v0.124.0->v0.125.0v0.124.0->v0.125.0v0.124.0->v0.125.0v0.124.0->v0.125.0v0.124.0->v0.125.0v0.124.0->v0.125.0Release Notes
open-telemetry/opentelemetry-collector-contrib (github.com/open-telemetry/opentelemetry-collector-contrib/exporter/elasticsearchexporter)
v0.125.0Compare Source
🛑 Breaking changes 🛑
awscloudwatchreceiver: Adds option to set storage for AWS CloudWatch receiver (#32231)start_fromfield in the logs config changed to Unix epoch (1970-01-01T00:00:00Z) when not explicitly configured. This may alter the behavior of existing configurations relying on the previous default.start_fromin the logs configuraiton.k8sobjectsreceiver: Check for K8s API objects existence on receiver startup and not during config validation. (#38803)receiver/kubeletstats: Move receiver.kubeletstats.enableCPUUsageMetrics feature gate to beta (#39487)Deprecated metrics
container.cpu.utilization,k8s.pod.cpu.utilizationandk8s.node.cpu.utilizationare being replacedby
container.cpu.usage,k8s.pod.cpu.usageandk8s.node.cpu.usage.To be able to use the deprecated metrics, switch
receiver.kubeletstats.enableCPUUsageMetricsfeature gate tofalse.processor/k8sattributes: Change processor/k8sattributes to return error if unset envvar is used fornode_from_env_var(#39447)Before this was a valid configuration, but had an unexpected behavior to monitor the entire cluster. | To keep the same behavior simply do not set the
node_from_env_varvalue or use empty string.sqlserverreceiver:host.name,sqlserver.computer.name, andsqlserver.instance.nameare now resource attributes instead of log attributes. We used to reportcomputer_nameandinstance_namein the log attributes for top query collection and they are now deprecated. Now we report the three resources attributes in both top query collection and sample query collection. (#39449)This change is only relevant for logs.
🚩 Deprecations 🚩
spanmetricsconnector: Deprecate the unused configurationdimensions_cache_size(#39646)Deprecated configuration
dimensions_cache_size, please useaggregation_cardinality_limitinstead🚀 New components 🚀
dnslookupprocessor: Add structure of new processor (#34398)datadogextension: Introduce framework for Datadog Extension (#39589)sematextexporter: basic logs implementation (#36465)💡 Enhancements 💡
spanmetricsconnector: Add newaggregation_cardinality_limitconfiguration option to limit the number of unique combinations of dimensions that will be tracked for metrics aggregation. (#38990)awslogsencodingextension: Add support for S3 Access Logs. (#39161)pkg: Improve performance of azure logs translator. (#39340)azureauthextension: Update stability to alpha. (#39574)countconnector: Add profiles support (#39577)awscloudwatchlogsexporter: Add dynamic log_group_name and log_group_stream naming, based on awsemfexporter (#31382)elasticsearchexporter: Add support for include_source_on_error, which configures whether bulk index responses should include source document on error (#39211)elasticsearchexporter: Introduce LRU cache for profiles (#38606)elasticsearchexporter: Add support for extracting mapping mode from a scope attribute. (#39110)opampextension: Introduces a new config fieldinclude_resource_attributeswhich allows the extension to copy the agent's resource attributes to the non-identifying attributes in the agent description. (#37487)statsdreceiver: Add new config to customize socket permissions when transport is set tounixgram. (#37807)kubeletstatsreceiver: Adds support for collecting Node and Pod network IO/error metrics for all network interfaces (#30196)awss3exporter: add configuration fieldresource_attrs_to_s3/s3_prefixto support mapping s3 bucket prefix to OTel resource attributes (#37858)If
resource_attrs_to_s3/s3_prefixis configured, s3 prefix will be determined based on the specified resource attribute ands3uploader/s3_prefixwill serve as a fallback.azureblobexporter: Add SerialNumBeforeExtension option to BlobNameFormat in Azure Blob exporter as an option to avoid breaking file extension (#39593)splunkhecexporter: Use ObservedTimestamp if Timestamp is empty. (#39221)githubreceiver: add dedicated job queue spans with cicd.pipeline.run.queue.duration attribute (#39081)hostmetricsreceiver: Possible to enable the process scraper under FreeBSD in the hostmetrics receiver. (#39622)k8sclusterreceiver: add support for k8s leader election in k8s cluster receiver (#38429)Allows multiple instances of the k8s cluster receiver to run in a HA mode in a single cluster.
kafkareceiver: Add support for configuring Kafka consumer rebalance strategy and group instance ID (#39513)This enhancement introduces two optional settings: group_rebalance_strategy and group_instance_id.
These allow users to override the default Range-based rebalance strategy and optionally provide a static instance ID (as per KIP-345) for cooperative sticky balancing.
This is particularly useful when handling high-cardinality metric workloads, as it reduces rebalance impact, improves cache reuse, and boosts CPU efficiency.
Both settings are optional to maintain full backward compatibility.
kafkareceiver: Added a new 'topic' attribute to all existing internal consume-claim metrics. (#35336)kafkareceiver: Addmax_fetch_waitconfig setting (#39360)This setting allows you to specify the maximum time that the broker will wait for
min_fetch_size bytes of data to be available before sending a response to the client.
Defaults to 250ms.
receiver_creator: Fix kafkametrics receiver instantiation (#39313)signaltometricsconnector: Add profiles support (#39609)sqlserverreceiver: Acceptcontext_infowithtraceparentformat in query sample collection, setting log record with correct traceId and spanId. (#39539)opampsupervisor: Add support for the opampsupervisor to be able to start with only local config (#38794)prometheusremotewritereceiver: Cachetarget_infometrics so it can be used to populate metrics' Resource Attributes. (#37277)You can read more about resource attributes handling in https://opentelemetry.io/docs/specs/otel/compatibility/prometheus_and_openmetrics/#resource-attributes-1
🧰 Bug fixes 🧰
sqlqueryreceiver: respectmax_open_connconfiguration for multiple queries (#39270)resourcedetectionprocessor: change the EKS cluster identifier and check the cluster version instead of the existence of aws-auth configmap (#39479)datadogexporter: Fix a race condition in metric serializer exporter where the exporter may not be fully initialized when it receives metrics (#39669)filelogreceiver: Fix frozen receiver when max_concurrent_files is 1 (#39598)transformprocessor: Fix the context inferrer to also take into consideration the global OTTL conditions configuration. (#39455)prometheusreceiver: When a histogram metric has both classic and native histogram buckets, keep both, instead of throwing away the native histogram buckets. (#26555)This was a technical dept from the previous implementation in PR 28663.
geoipprocessor: Close providers readers on shutdown (#38961)receivercreator: Fix how escaped backticks are handled in receiver creator templates (#39163)opampsupervisor: Supervisor will no longer report a config status of "applying" if the config has not changed (#39500)githubreceiver: Fix span end times for skipped and cancelled workflows (#39020)k8sobjectsreceiver: Introduceserror_mode, so users can choose between propagating, ignoring, or silencing missing objects. (#38803)opampextension: Skips loading TLS config for insecure endpoints (#39515)opampsupervisor: fixes OpAMP Supervisor macOS example config (#39492)tcpcheckreceiver: Fix tcpcheck.error to report as a cumulative value instead of always being 1. (#39234)kafkareceiver:namelabel will be correctly set in receiver metrics (#39483)signaltometricsconnector: Fix incorrect result for metrics configured with same name but different type (#39442)tcplogreceiver: Ignore SplitFuncBuilder field to prevent panic during config marshaling (#39474)deltatocumulative: fixes misuse of xsync, leading to bad mutex unlock (#39106)open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector/confmap/provider/envprovider)
v1.31.0🛑 Breaking changes 🛑
service: Lowercase values for 'otelcol.component.kind' attributes. (#12865)service: Restrict thetelemetry.newPipelineTelemetryfeature gate to metrics. (#12856, #12933)The "off" state of this feature gate introduced a regression, where the Collector's internal logs were missing component attributes. See issue #12870 for more details on this bug.
On the other hand, the "on" state introduced an issue with the Collector's default internal metrics, because the Prometheus exporter does not currently support instrumentation scope attributes.
To solve both of these issues, this change turns on the new scope attributes for logs and traces by default regardless of the feature gate.
However, the new scope attributes for metrics stay locked behind the feature gate, and will remain off by default until the Prometheus exporter is updated to support scope attributes.
Please understand that enabling the
telemetry.newPipelineTelemetryfeature gate may break the export of Collector metrics through, depending on your configuration.Having a
batchprocessor in multiple pipelines is a known trigger for this.This comes with a breaking change, where internal logs exported through OTLP will now use instrumentation scope attributes to identify the source component instead of log attributes.
This does not affect the Collector's stderr output. See the changelog for v0.123.0 for a more detailed description of the gate's effects.
💡 Enhancements 💡
mdatagen: Add support for attributes for telemetry configuration in metadata. (#12919)configmiddleware: Add extensionmiddleware interface. (#12603, #9591)configgrpc: Add gRPC middleware support. (#12603, #9591)confighttp: Add HTTP middleware support. (#12603, #9591, #7441)configmiddleware: Add configmiddleware struct. (#12603, #9591)🧰 Bug fixes 🧰
exporterhelper: Do not ignore thenum_consumerssetting when batching is enabled. (#12244)exporterhelper: Reject elements larger than the queue capacity (#12847)mdatagen: Add time and plog package imports (#12907)confmap: Maintain nil values when marshaling or unmarshaling nil slices (#11882)Previously, nil slices were converted to empty lists, which are semantically different
than a nil slice. This change makes this conversion more consistent when encoding
or decoding config, and these values are now maintained.
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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.