⬆️ Update module go.opentelemetry.io/collector to v0.138.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
go.opentelemetry.io/collector	v0.91.0 -> v0.138.0

---

Release Notes

open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector)

v0.138.0

Compare Source

🛑 Breaking changes 🛑

• all: Remove deprecated type TracesConfig (#​14036)

• pkg/exporterhelper: Add default values for sending_queue::batch configuration. (#​13766)
  Setting sending_queue::batch to 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-config command. See the service package README for more details. The original command name print-initial-config remains an alias, to be retired with the feature flag.

💡 Enhancements 💡

• all: Add keep_alives_enabled option 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 use pcommon.Value instead of AnyValue. (#​13837)
• pkg/exporterhelper: Expose MergeCtx in 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)

v0.137.0

Compare Source

💡 Enhancements 💡

• cmd/mdatagen: Improve validation for resource attribute enabled field in metadata files (#​12722)
  Resource attributes now require an explicit enabled field in metadata.yaml files, while regular attributes
  are 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)

v0.136.0

Compare Source

💡 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)

v0.135.0

Compare Source

💡 Enhancements 💡

• exporterhelper: Add new exporter_queue_batch_send_size and exporter_queue_batch_send_size_bytes metrics, showing the size of telemetry batches from the exporter. (#​12894)

v0.134.0

Compare Source

💡 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: Respect num_consumers when 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.

v0.133.0

Compare Source

🛑 Breaking changes 🛑

• all: Increase minimum Go version to 1.24 (#​13627)

💡 Enhancements 💡

• otlphttpexporter: Add profiles_endpoint configuration option to allow custom endpoint for profiles data export (#​13504)
  The profiles_endpoint configuration follows the same pattern as traces_endpoint, metrics_endpoint, and logs_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 new otelcol_receiver_failed_x and otelcol_receiver_requests metrics (#​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.newReceiverMetrics feature 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.useCustomProtoEncoding

• configtls: 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.Optional now implements xconfmap.Validator
• batchprocessor: 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.

v0.132.0

Compare Source

🛑 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:

  service:
    telemetry:
      traces:
        level: none
  

• mdatagen: Remove the deletion of generated_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: The telemetry.disableHighCardinalityMetrics feature 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:

  service:
    telemetry:
      metrics:
        level: detailed
        views:
          - selector:
              meter_name: "go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc"
            stream:
              attribute_keys:
                excluded: ["net.sock.peer.addr", "net.sock.peer.port", "net.sock.peer.name"]
          - selector:
              meter_name: "go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp"
            stream:
              attribute_keys:
                excluded: ["net.host.name", "net.host.port"]

  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)

v0.131.0

Compare Source

🛑 Breaking changes 🛑

• confighttp: Move confighttp.framedSnappy feature gate to beta. (#​10584)

💡 Enhancements 💡

• exporter/debug: Move to alpha stability except profiles (#​13487)

• exporterhelper: Enable exporter.PersistRequestContext feature 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:

  • "outcome = failure" indicates that the component returned an internal error;
  • "outcome = refused" indicates that the component successfully emitted data, but returned an
    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 enables otel_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 of DIST_* environment variables replacements (#​13335)

v0.130.1

Compare Source

🧰 Bug fixes 🧰

• service: Fixes bug where internal metrics are emitted with an unexpected suffix in their names when users configure service::telemetry::metrics::readers with Prometheus. (#​13449)
  See more details on open-telemetry/opentelemetry-go#7039

v0.130.0

Compare Source

❗ 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__total instead of otelcol_exporter_sent_spans_total. The workaround is to manually configure without_units: true in your prometheus exporter config

  service:
    telemetry:
      metrics:
        readers:
          - pull:
              exporter:
                prometheus:
                  host: 0.0.0.0
                  port: 8888
                  without_units: true

  If 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: Replaced sigs.k8s.io/yaml with go.yaml.in/yaml for 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.go could
  cause the name field of some metrics to disappear. This fix ensures that all metric fields are
  properly preserved when metricRequest objects are split.

• service: Default internal metrics config now enables otel_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, and otel_scope_version labels corresponding to the
  instrumentation 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.

v0.129.0

Compare Source

🛑 Breaking changes 🛑

• exporterhelper: Remove deprecated sending_queue::blocking options, use sending_queue::block_on_overflow. (#​13211)

💡 Enhancements 💡

• mdatagen: Taught mdatagen to print the go list stderr output on failures, and to run go list where the metadata file is. (#​13205)

• service: Support setting sampler and limits under service::telemetry::traces (#​13201)
  This allows users to enable sampling and set span limits on internal Collector traces using the
  OpenTelemetry SDK declarative configuration.

• pdata/pprofile: Add new helper methods FromLocationIndices and PutLocation to read and modify the content of locations. (#​13150)

• exporterhelper: Preserve request span context and client information in the persistent queue. (#​11740, #​13220, #​13232)
  It allows internal collector spans and client information to propagate through the persistent queue used by
  the exporters. The same way as it's done for the in-memory queue.
  Currently, it is behind the exporter.PersistRequestContext feature gate, which can be enabled by adding
  --feature-gates=exporter.PersistRequestContext to the collector command line. An exporter buffer stored by
  a previous version of the collector (or by a collector with the feature gate disabled) can be read by a newer
  collector with the feature enabled. However, the reverse is not supported: a buffer stored by a newer collector with
  the feature enabled cannot be read by an older collector (or by a collector with the feature gate disabled).

🧰 Bug fixes 🧰

• pdata: Fix copying of optional fields when the source is unset. (#​13268)
• service: Only allocate one set of internal log sampling counters (#​13014)
  The case where logs are only exported to stdout was fixed in v0.126.0;
  this new fix also covers the case where logs are exported through OTLP.

v0.128.0

Compare Source

🛑 Breaking changes 🛑

• service/telemetry: Mark "telemetry.disableAddressFieldForInternalTelemetry" as stable (#​13152)

💡 Enhancements 💡

• confighttp: Update the HTTP server span naming to use the HTTP method and route pattern instead of the path. (#​12468)
  The HTTP server span name will now be formatted as <http.request.method> <http.route>.
  If a route pattern is not available, it will fall back to <http.request.method>.

• service: Use configured loggers to log errors as soon as it is available (#​13081)

• service: Remove stabilized featuregate useOtelWithSDKConfigurationForInternalTelemetry (#​13152)

🧰 Bug fixes 🧰

• telemetry: Add generated resource attributes to the printed log messages. (#​13110)
  If service.name, service.version, or service.instance.id are not specified in the config, they will be generated automatically.
  This change ensures that these attributes are also included in the printed log messages.

• mdatagen: Fix generation when there are no events in the metadata. (#​13123)

• confmap: Do not panic on assigning nil maps to non-nil maps (#​13117)

• pdata: Fix event_name skipped when unmarshalling LogRecord from JSON (#​13127)

v0.127.0

Compare Source

🚩 Deprecations 🚩

• semconv: Deprecating the semconv package in favour of go.opentelemetry.io/otel/semconv (#​13012)

💡 Enhancements 💡

• exporter/debug: Display resource and scope in normal verbosity (#​10515)
• service: Add size metrics defined in Pipeline Component Telemetry RFC (#​13032)
  See Pipeline Component Telemetry RFC for more details:
  • otelcol.receiver.produced.size
  • otelcol.processor.consumed.size
  • otelcol.processor.produced.size
  • otelcol.connector.consumed.size
  • otelcol.connector.produced.size
  • otelcol.exporter.consumed.size

v0.126.0

Compare Source

🛑 Breaking changes 🛑

• configauth: Removes deprecated configauth.Authentication and extensionauthtest.NewErrorClient (#​12992)
  The following have been removed:
  • configauth.Authentication use configauth.Config instead
  • extensionauthtest.NewErrorClient use extensionauthtest.NewErr instead

💡 Enhancements 💡

• service: Replace go.opentelemetry.io/collector/semconv usage with go.opentelemetry.io/otel/semconv (#​12991)

• confmap: Update the behavior of the confmap.enableMergeAppendOption feature gate to merge only component lists. (#​12926)

• service: Add item count metrics defined in Pipeline Component Telemetry RFC (#​12812)
  See Pipeline Component Telemetry RFC for more details:

  • otelcol.receiver.produced.items
  • otelcol.processor.consumed.items
  • otelcol.processor.produced.items
  • otelcol.connector.consumed.items
  • otelcol.connector.produced.items
  • otelcol.exporter.consumed.items

• tls: Add trusted platform module (TPM) support to TLS authentication. (#​12801)
  Now the TLS allows the use of TPM for loading private keys (e.g. in TSS2 format).

🧰 Bug fixes 🧰

• exporterhelper: Add validation error for batch config if min_size is greater than queue_size. (#​12948)

• telemetry: Allocate less memory per component when OTLP exporting of logs is disabled (#​13014)

• confmap: Use reflect.DeepEqual to avoid panic when confmap.enableMergeAppendOption feature gate is enabled. (#​12932)

• internal telemetry: Add resource attributes from telemetry.resource to the logger (#​12582)
  Resource attributes from telemetry.resource were not added to the internal
  console logs.

  Now, they are added to the logger as part of the "resource" field.

• confighttp and configcompression: Fix handling of snappy content-encoding in a backwards-compatible way (#​10584, #​12825)
  The collector used the Snappy compression type of "framed" to handle the HTTP
  content-encoding "snappy". However, this encoding is typically used to indicate
  the "block" compression variant of "snappy". This change allows the collector to:

  • When receiving a request with encoding 'snappy', the server endpoints will peek
    at the first bytes of the payload to determine if it is "framed" or "block" snappy,
    and will decompress accordingly. This is a backwards-compatible change.

  If the feature-gate "confighttp.framedSnappy" is enabled, you'll see new behavior for both client and server:

  • Client compression type "snappy" will now compress to the "block" variant of snappy
    instead of "framed". Client compression type "x-snappy-framed" will now compress to the "framed" variant of snappy.
  • Servers will accept both "snappy" and "x-snappy-framed" as valid content-encodings.

• tlsconfig: Disable TPM tests on MacOS/Darwin (#​12964)

v0.125.0

Compare Source

🛑 Breaking changes 🛑

• service: Lowercase values for 'otelcol.component.kind' attributes. (#​12865)

• service: Restrict the telemetry.newPipelineTelemetry feature 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.newPipelineTelemetry feature gate may break the export of Collector metrics through, depending on your configuration.
  Having a batch processor 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 the num_consumers setting 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.

v0.124.0

Compare Source

💡 Enhancements 💡

• exporterhelper: Add support for bytes-based batching for profiles in the exporterhelper package. (#​3262)
• otelcol: Enhance config validation using command to capture all validation errors that prevents the collector from starting. (#​8721)
• exporterhelper: Link batcher context to all batched request's span contexts. (#​12212, #​8122)

🧰 Bug fixes 🧰

• confighttp: Ensure http authentication server failures are handled by the provided error handler (#​12666)

v0.123.0

Compare Source

❗ Known Issues ❗

• This version increases memory usage by ~0.5 MB per component in the pipelines because a separate Zap Core logger is
  initialized for each component. The issue is partially fixed in v0.126.0 for users who write logs to stdout, but do
  not export logs via OTLP. See #​13014 for more details.

🛑 Breaking changes 🛑

• service/telemetry: Mark telemetry.disableAddressFieldForInternalTelemetry as beta, usage of deprecated service::telemetry::address are ignored (#​25115)
  To restore the previous behavior disable telemetry.disableAddressFieldForInternalTelemetry feature gate.
• exporterbatch: Remove deprecated fields min_size_items and max_size_items from batch config. (#​12684)

🚩 Deprecations 🚩

• otlpexporter: Mark BatcherConfig as deprecated, use sending_queue::batch instead (#​12726)
• exporterhelper: Deprecate blocking in favor of block_on_overflow. (#​12710)
• exporterhelper: Deprecate configuring exporter batching separately. Use sending_queue::batch instead. (#​12772)
  Moving the batching configuration to sending_queue::batch requires setting sending_queue::sizer to items
  which means that sending_queue::queue_size needs to be also increased by the average batch size number (roughly
  x5000 for the default batching configuration).
  See https://github.com/open-telemetry/opentelemetry-collector/tree/main/exporter/exporterhelper#configuration

💡 Enhancements 💡

• exporterhelper: Add support to configure batching in the sending queue. (#​12746)

• exporterhelper: Add support for wait_for_result, remove disabled_queue (#​12742)
  This has a side effect for users of the experimental BatchConfig with the queue disabled, since not this is | uses only NumCPU() consumers.

• exporterhelper: Allow exporter memory queue to use different type of sizers. (#​12708)

• service: Add "telemetry.newPipelineTelemetry" feature gate to inject component-identifying attributes in internal telemetry (#​12217)
  With the feature gate enabled, all internal telemetry (metrics/traces/logs) will include some of
  the following instrumentation scope attributes:

  • otelcol.component.kind
  • otelcol.component.id
  • otelcol.pipeline.id
  • otelcol.signal
  • otelcol.signal.output

  These attributes are defined in the Pipeline Component Telemetry RFC,
  and identify the component instance from which the telemetry originates.
  They are added automatically without changes to component code.

  These attributes were already included in internal logs as regular log attributes, starting from
  v0.120.0. For consistency with other signals, they have been switched to scope attributes (with
  the exception of logs emitted to standard output), and are now enabled by the feature gate.

  Please make sure that the exporter / backend endpoint you use has support for instrumentation
  scope attributes before using this feature. If the internal telemetry is exported to another
  Collector, a transform processor could be used to turn them into other kinds of attributes if
  necessary.

• exporterhelper: Enable support to do batching using bytes sizer (#​12751)

• service: Add config key to set metric views used for internal telemetry (#​10769)
  The service::telemetry::metrics::views config key can now be used to explicitly set the list of
  metric views used for internal telemetry, mirroring meter_provider::views in the SDK config.
  This can be used to disable specific internal metrics, among other uses.

  This key will cause an error if used alongside other features which would normally implicitly create views, such as:

  • not setting service::telemetry::metrics::level to detailed;
  • enabling the telemetry.disableHighCardinalityMetrics feature flag.

🧰 Bug fixes 🧰

• exporterhelper: Fix order of starting between queue and batch. (#​12705)

v0.122.1

Compare Source

🧰 Bug fixes 🧰

• confmap: Ensure slices with defaults containing struct values are correctly set. (#​12661)
  This reverts the changes made in #​11882.

v0.122.0

Compare Source

🛑 Breaking changes 🛑

• service: Batch processor telemetry is no longer emitted at "basic" verbosity level (#​7890)
  According to the guidelines, basic-level telemetry should be reserved for core Collector APIs.
  Components such as the batch processor should emit telemetry starting from the "normal" level
  (which is also the default level).

  Migration: If your Collector telemetry was set to level: basic and you want to keep seeing
  batch processor-related metrics, consider switching to level: normal instead.

💡 Enhancements 💡

• service: Add service.AllowNoPipelines feature gate to allow starting the Collector without pipelines. (#​12613)
  This can be used to start with only extensions.

• mdatagen: Delete generated_status.go if the component type doesn't require it. (#​12346)

• componenttest: Improve config struct mapstructure field tag checks (#​12590)
  remain tags and omitempty tags without a custom field name will now pass validation.

• service: include component id/type in start error (#​10426)

• mdatagen: Add deprecation date and migration guide fields as part of component metadata (#​12359)

• confmap: Introduce a new feature flag to allow for merging lists instead of discarding the existing ones. (#​8394, #​8754, #​10370)
  You can enable this option via the command line by running following command:
  otelcol --config=main.yaml --config=extra_config.yaml --feature-gates=-confmap.enableMergeAppendOption

• zpagesextension: Add expvar handler to zpages extension. (#​11081)

🧰 Bug fixes 🧰

• 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.

• service: do not attempt to register process metrics if they are disabled (#​12098)

v0.121.0

Compare Source

🛑 Breaking changes 🛑

• confighttp: Make the client config options max_idle_conns, max_idle_conns_per_host, max_conns_per_host, and idle_conn_timeout integers (#​9478)
  All four options can be set to 0 where they were previously set to null

🚩 Deprecations 🚩

• exporterhelper: Deprecate min_size_items and max_size_items in favor of min_size and max_size. (#​12486)

💡 Enhancements 💡

• mdatagen: Add converter and provider module classes (#​12467)

• pipeline: output pipeline name with signal as signal[/name] format in logs. (#​12410)

• memorylimiter: Add support to configure min GC intervals for soft and hard limits. (#​12450)

• otlpexporter: Update the stability level for logs, it has been as stable as traces and metrics for some time. (#​12423)

• service: Create a new subcommand to dump the initial configuration after resolving/merging. (#​11479)
  To use the print-initial-config subcommand, invoke the Collector with the subcommand and corresponding feature gate: otelcol print-initial-config --feature-gates=otelcol.printInitialConfig --config=config.yaml.
  Note that the feature gate enabling this flag is currently in alpha stability, and the subcommand may
  be changed in the future.

• memorylimiterprocessor: Add support for profiles. (#​12453)

• otelcol: Converters are now available in the components command. (#​11900, #​12385)

• component: Mark module as stable (#​9376)

• confmap: Surface YAML parsing errors when they happen at the top-level. (#​12180)
  This adds context to some instances of the error "retrieved value (type=string) cannot be used as a Conf", which typically happens because of invalid YAML documents

• pprofile: Add LinkIndex attribute to the generated Sample type (#​12485)

• exporterhelper: Stabilize exporter.UsePullingBasedExporterQueueBatcher and remove old batch sender (#​12425)

• mdatagen: Update metadata schema with new fields without enforcing them (#​12359)

🧰 Bug fixes 🧰

• service: Fix crash at startup when converting from v0.2.0 to v0

---

Configuration

📅 Schedule: Branch creation - "before 2am" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (94cf978) 73.39% compared to head (dc38103) 73.39%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #119   +/-   ##
=======================================
  Coverage   73.39%   73.39%           
=======================================
  Files           2        2           
  Lines         109      109           
=======================================
  Hits           80       80           
  Misses         20       20           
  Partials        9        9           

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