chore(deps): update otel-collector upstream dependencies to v0.103.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence	Type	Update
github.com/open-telemetry/opentelemetry-collector-contrib/exporter/kafkaexporter	v0.102.0 -> v0.103.0					exports	minor
github.com/open-telemetry/opentelemetry-collector-contrib/exporter/loadbalancingexporter	v0.102.0 -> v0.103.0					exports	minor
github.com/open-telemetry/opentelemetry-collector-contrib/extension/basicauthextension	v0.102.0 -> v0.103.0					extensions	minor
github.com/open-telemetry/opentelemetry-collector-contrib/extension/bearertokenauthextension	v0.102.0 -> v0.103.0					extensions	minor
github.com/open-telemetry/opentelemetry-collector-contrib/extension/healthcheckextension	v0.102.0 -> v0.103.0					extensions	minor
github.com/open-telemetry/opentelemetry-collector-contrib/extension/oauth2clientauthextension	v0.102.0 -> v0.103.0					extensions	minor
github.com/open-telemetry/opentelemetry-collector-contrib/extension/oidcauthextension	v0.102.0 -> v0.103.0					extensions	minor
github.com/open-telemetry/opentelemetry-collector-contrib/extension/pprofextension	v0.102.0 -> v0.103.0					extensions	minor
github.com/open-telemetry/opentelemetry-collector-contrib/processor/probabilisticsamplerprocessor	v0.102.0 -> v0.103.0					processors	minor
github.com/open-telemetry/opentelemetry-collector-contrib/processor/tailsamplingprocessor	v0.102.0 -> v0.103.0					processors	minor
github.com/open-telemetry/opentelemetry-collector-contrib/receiver/jaegerreceiver	v0.102.0 -> v0.103.0					receivers	minor
github.com/open-telemetry/opentelemetry-collector-contrib/receiver/kafkareceiver	v0.102.0 -> v0.103.0					receivers	minor
github.com/open-telemetry/opentelemetry-collector-contrib/receiver/zipkinreceiver	v0.102.0 -> v0.103.0					receivers	minor
go.opentelemetry.io/collector	0.102.1 -> 0.103.0					collector	minor
go.opentelemetry.io/collector/exporter/nopexporter	v0.102.1 -> v0.103.0					exports	minor
go.opentelemetry.io/collector/exporter/otlpexporter	v0.102.1 -> v0.103.0					exports	minor
go.opentelemetry.io/collector/exporter/otlphttpexporter	v0.102.1 -> v0.103.0					exports	minor
go.opentelemetry.io/collector/receiver/otlpreceiver	v0.102.1 -> v0.103.0					receivers	minor
open-telemetry/opentelemetry-collector	0.102.1 -> 0.103.0						minor

---

Release Notes

open-telemetry/opentelemetry-collector-contrib (github.com/open-telemetry/opentelemetry-collector-contrib/exporter/kafkaexporter)

v0.103.0

Compare Source

🛑 Breaking changes 🛑

• cmd/opampsupervisor,extension/opamp: Upgrade the opamp-go library to v0.15.0 (#​33416)
  With this change, UUIDv7 is recommended for the OpAMP extension's instance_uid field instead of ULID. ULIDs will continue to work, but may be displayed as UUIDs.
  The supervisor's persistent state (${storage_dir}/persistent_state.yaml) will need to be cleared to generate a new UUIDv7 instead of a ULID.
  This change may be incompatible with management servers using v0.14.0 of opamp-go.

• mongodbreceiver: Now only supports TCP connections (#​32199)
  This fixes a bug where hosts had to explicitly set tcp as the transport type. The transport option has been removed.

• cmd/configschema: Removes the deprecated configschema command. This command will no longer be released or supported. (#​33384)

• sqlserverreceiver: sqlserver.database.io.read_latency has been renamed to sqlserver.database.latency with a direction attribute. (#​29865)

🚩 Deprecations 🚩

• healthcheckextension: Remove incorrect logic behind check_collector_pipeline config (#​33469)
  This logic incorrectly set the pipeline to OK after waiting for enough callbacks from the
  opencensus library to be called. As this was broken, I'm removing it to remove the dependency
  on opencensus as well. Improvements will be available via healthcheckv2 extension.

• googlecloudspannerreceiver: Mark the component as unmaintained. If we don't find new maintainers, it will be deprecated and removed. (#​32651)

💡 Enhancements 💡

• filelogreceiver: If include_file_record_number is true, it will add the file record number as the attribute log.file.record_number (#​33530)

• kubeletstats: Add k8s.pod.cpu.node.utilization metric (#​33390)

• awss3exporter: endpoint should contain the S3 bucket (#​32774)

• awss3receiver: Add support for encoding extensions to be used in the AWS S3 Receiver. (#​30750)

• gitproviderreceiver: Adds branch commit and line based metrics (#​22028)
  Adds the following branch based metrics.

  • git.repository.branch.time
  • git.repository.branch.commit.aheadby.count
  • git.repository.branch.commit.behindby.count
  • git.repository.branch.line.deletion.count
  • git.repository.branch.line.addition.count

• statsdreceiver: update statsd receiver to use mdatagen (#​33524)

• coralogixexporter: Allow setting application name from cx.application.name and cx.subsystem.name resource attributes (#​33217)

• metricstransformprocessor: Adds the 'count' aggregation type to the Metrics Transform Processor. (#​24978)

• elasticsearchexporter: Add support for confighttp options, notably "auth". (#​33367)
  Add support for confighttp and related configuration settings, such as "auth".
  This change also means that the Elasticsearch URL may be specified as "endpoint",
  like the otlphttp exporter.

• elasticsearchexporter: Check that endpoints are valid URLs during config validation. (#​33350)
  Check that endpoints are valid URLs during config validation so that
  an invalid endpoint causes a fatal error during startup, rather than
  leading to a persistent runtime error.

• opampsupervisor: Add config validation for the supervisor config (#​32843)

• statsdreceiver: Added received/accepted/refused metrics (#​24278)

• filelogreceiver: Add support for gzip compressed log files (#​2328)

• confmap/provider/secretsmanagerprovider: Add support for JSON formatted secrets in secretsmanagerprovider confmap (#​32143)
  The secretsmanagerprovider confmap will now allow to get secret by a json key if the secret value is json.
  To specify key separate key from secret name/arn by # e.g. mySecret#mySecretKey.

• geoipprocessor: Add initial processing based on source.address resource attribute (#​32663)

• healthcheckv2extension: Add shared aggregation logic for status events. (#​26661)

• tailsamplingprocessor: Simple LRU Decision Cache for "keep" decisions (#​31583)

• processor/tailsampling: Migrates internal telemetry to OpenTelemetry SDK via mdatagen (#​31581)
  The metric names and their properties, such as bucket boundaries for histograms, were kept like before, to keep backwards compatibility.

• kafka: Added disable_fast_negotiation configuration option for Kafka Kerberos authentication, allowing the disabling of PA-FX-FAST negotiation. (#​26345)

• pkg/ottl: Added keep_matching_keys function to allow dropping all keys from a map that don't match the pattern. (#​32989)

• OTel-Arrow: Update to OTel-Arrow v0.24.0 (#​26491)

• pkg/ottl: Add debug logs to help troubleshoot OTTL statements/conditions (#​33274)

• pkg/ottl: Introducing append function for appending items into an existing array (#​32141)

• pkg/ottl: Introducing Uri converter parsing URI string into SemConv (#​32433)

• probabilisticsamplerprocessor: Add Proportional and Equalizing sampling modes (#​31918)
  Both the existing hash_seed mode and the two new modes use OTEP 235 semantic conventions to encode sampling probability.

• prometheusreceiver: Resource attributes produced by the prometheus receiver now include stable semantic conventions for server and url. (#​32814)
  To migrate from the legacy net.host.name, net.host.port, and http.scheme resource attributes, |
  migrate to server.address, server.port, and url.scheme, and then |
  set the receiver.prometheus.removeLegacyResourceAttributes feature gate.

• datadogexporter: The Datadog Exporter now supports the proxy_url parameter to configure an HTTP proxy to use when sending telemetry to Datadog. (#​33316)

• spanmetrics: Produce delta temporality span metrics with StartTimeUnixNano and TimeUnixNano values representing an uninterrupted series (#​31671, #​30688)
  This allows producing delta span metrics instead of the more memory-intensive cumulative metrics, specifically when a downstream component can convert the delta metrics to cumulative.

• sqlserverreceiver: Add support for more Database IO metrics (#​29865)
  The following metrics have been added:

  • sqlserver.database.latency
  • sqlserver.database.io
  • sqlserver.database.operations

• cmd/opampsupervisor: Receive and report effective config to the OpAMP server (#​30622)

• processor/transform: Add transform.flatten.logs featuregate to give each log record a distinct resource and scope. (#​32080)
  This option is useful when applying transformations which alter the resource or scope. e.g. set(resource.attributes["to"], attributes["from"]), which may otherwise result in unexpected behavior. Using this option typically incurs a performance penalty as the processor must compute many hashes and create copies of resource and scope information for every log record.

• receiver/windowsperfcounters: Counter configuration now supports recreating the underlying performance query at scrape time. (#​32798)

🧰 Bug fixes 🧰

• filelogreceiver: Container parser should add k8s metadata as resource attributes and not as log record attributes (#​33341)
• deltatocumulative: properly drop samples when at limit (#​33285)
  fixes a segfault in the limiting behavior, where streams exceeding the limit still had their samples processed. due to not being tracked, this led to a nil-pointer deref
• postgresqlreceiver: Fix bug where postgresql.rows always returning 0 for state="dead" (#​33489)
• prometheusreceiver: Fall back to scrape config job/instance labels for aggregated metrics without instance/job labels (#​32555)
• elasticsearchexporter: Duplicate Key in JSON (#​33454)
• logzioexporter: Fix issue where log attributes were not correctly exported (#​33231)
• exporter/datadog: Prevents collector shut down when Datadog logs pipeline fails to validate API key (#​33195)

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

v0.103.0

Compare Source

🛑 Breaking changes 🛑

• exporter/debug: Disable sampling by default (#​9921)
  To restore the behavior that was previously the default, set sampling_thereafter to 500.

💡 Enhancements 💡

• cmd/builder: Allow setting otelcol.CollectorSettings.ResolverSettings.DefaultScheme via the builder's conf_resolver.default_uri_scheme configuration option (#​10296)
• mdatagen: add support for optional internal metrics (#​10316)
• otelcol/expandconverter: Add confmap.unifyEnvVarExpansion feature gate to allow enabling Collector/Configuration SIG environment variable expansion rules. (#​10391)
  When enabled, this feature gate will:
  • Disable expansion of BASH-style env vars ($FOO)
  • ${FOO} will be expanded as if it was `${env:FOO}
    See https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/rfcs/env-vars.md for more details.
• confmap: Add confmap.unifyEnvVarExpansion feature gate to allow enabling Collector/Configuration SIG environment variable expansion rules. (#​10259)
  When enabled, this feature gate will:
  • Disable expansion of BASH-style env vars ($FOO)
  • ${FOO} will be expanded as if it was `${env:FOO}
    See https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/rfcs/env-vars.md for more details.
• confighttp: Allow the compression list to be overridden (#​10295)
  Allows Collector administrators to control which compression algorithms to enable for HTTP-based receivers.
• configgrpc: Revert the zstd compression for gRPC to the third-party library we were using previously. (#​10394)
  We switched back to our compression logic for zstd when a CVE was found on the third-party library we were using. Now that the third-party library has been fixed, we can revert to that one. For end-users, this has no practical effect. The reproducers for the CVE were tested against this patch, confirming we are not reintroducing the bugs.
• confmap: Adds alpha confmap.strictlyTypedInput feature gate that enables strict type checks during configuration resolution (#​9532)
  When enabled, the configuration resolution system will:
  • Stop doing most kinds of implicit type casting when resolving configuration values
  • Use the original string representation of configuration values if the ${} syntax is used in inline position
• confighttp: Use confighttp.ServerConfig as part of zpagesextension. See [https://github.com/open-telemetry/opentelemetry-collector/blob/main/config/confighttp/README.md#server-configuration]\(server configuration) options. (#​9368)

🧰 Bug fixes 🧰

• exporterhelper: Fix potential deadlock in the batch sender (#​10315)
• expandconverter: Fix bug where an warning was logged incorrectly. (#​10392)
• exporterhelper: Fix a bug when the retry and timeout logic was not applied with enabled batching. (#​10166)
• exporterhelper: Fix a bug where an unstarted batch_sender exporter hangs on shutdown (#​10306)
• exporterhelper: Fix small batch due to unfavorable goroutine scheduling in batch sender (#​9952)
• confmap: Fix issue where structs with only yaml tags were not marshaled correctly. (#​10282)

---

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.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.