Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update otel-collector upstream dependencies to v0.100.0 #53

Merged
merged 1 commit into from
May 7, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 6, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
github.com/open-telemetry/opentelemetry-collector-contrib/exporter/loadbalancingexporter v0.99.0 -> v0.100.0 age adoption passing confidence exports minor
github.com/open-telemetry/opentelemetry-collector-contrib/extension/healthcheckextension v0.99.0 -> v0.100.0 age adoption passing confidence extensions minor
github.com/open-telemetry/opentelemetry-collector-contrib/receiver/jaegerreceiver v0.99.0 -> v0.100.0 age adoption passing confidence receivers minor
github.com/open-telemetry/opentelemetry-collector-contrib/receiver/zipkinreceiver v0.99.0 -> v0.100.0 age adoption passing confidence receivers minor
go.opentelemetry.io/collector 0.99.0 -> 0.100.0 age adoption passing confidence collector minor
go.opentelemetry.io/collector/exporter/otlpexporter v0.99.0 -> v0.100.0 age adoption passing confidence exports minor
go.opentelemetry.io/collector/receiver/otlpreceiver v0.99.0 -> v0.100.0 age adoption passing confidence receivers minor
open-telemetry/opentelemetry-collector 0.99.0 -> 0.100.0 age adoption passing confidence minor

Release Notes

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

v0.100.0

Compare Source

🛑 Breaking changes 🛑
  • receiver/hostmetrics: enable feature gate receiver.hostmetrics.normalizeProcessCPUUtilization (#​31368)
    This changes the value of the metric process.cpu.utilization by dividing it by the number of CPU cores.
    For example, if a process is using 2 CPU cores on a 16-core machine,
    the value of this metric was previously 2, but now it will be 0.125.

  • testbed: Remove deprecated GetAvailablePort function (#​32800)

🚀 New components 🚀
  • healthcheckv2extension: Introduce the skeleton for the temporary healthcheckv2 extension. (#​26661)
  • intervalprocessor: Implements the new interval processor. See the README for more info about how to use it (#​29461)
  • OpenTelemetry Protocol with Apache Arrow Receiver: Implementation copied from opentelemetry/otel-arrow repository @​v0.20.0. (#​26491)
  • roundrobinconnector: Add a roundrobin connector, that can help single thread components to scale (#​32853)
💡 Enhancements 💡
  • telemetrygen: Add support to set metric name (#​32840)

  • exporter/kafkaexporter: Enable setting message topics using resource attributes. (#​31178)

  • exporter/datadog: Introduces the Datadog Agent logs pipeline for exporting logs to Datadog under the "exporter.datadogexporter.UseLogsAgentExporter" feature gate. (#​32327)

  • elasticsearchexporter: Add retry.retry_on_status config (#​32584)
    Previously, the status codes that trigger retries were hardcoded to be 429, 500, 502, 503, 504.
    It is now configurable using retry.retry_on_status, and defaults to [429, 500, 502, 503, 504] to avoid a breaking change.
    To avoid duplicates, it is recommended to configure retry.retry_on_status to [429], which would be the default in a future version.

  • exporter/splunkhec: add experimental exporter batcher config (#​32545)

  • windowsperfcountersreceiver: Returns partial errors for failures during scraping to prevent throwing out all successfully retrieved metrics (#​16712)

  • jaegerencodingextension: Promote jaegerencodingextension to alpha (#​32699)

  • kafkaexporter: add an ability to publish kafka messages with message key based on metric resource attributes - it will allow partitioning metrics in Kafka. (#​29433, #​30666, #​31675)

  • cmd/opampsupervisor: Switch the OpAMP Supervisor's bootstrap config to use the nopreceiver and nopexporter (#​32455)

  • otlpencodingextension: Move otlpencodingextension to alpha (#​32701)

  • prometheusreceiver: Prometheus receivers and exporters now preserve 'unknown', 'info', and 'stateset' types. (#​16768)
    It uses the metric.metadata field with the 'prometheus.type' key to store the original type.

  • ptracetest: Add support for ignore scope span instrumentation scope information (#​32852)

  • sqlserverreceiver: Enable direct connection to SQL Server (#​30297)
    Directly connecting to SQL Server will enable the receiver to gather more metrics
    for observing the SQL Server instance. The first metric added with this update is
    sqlserver.database.io.read_latency.

  • connector/datadog: The Datadog connector now has a config option to identify top-level spans by span kind. This new logic can be enabled by setting traces::compute_top_level_by_span_kind to true in the Datadog connector config. Default is false. (#​32005)
    traces::compute_top_level_by_span_kind needs to be enabled in both the Datadog connector and Datadog exporter configs if both components are being used.
    With this new logic, root spans and spans with a server or consumer span.kind will be marked as top-level. Additionally, spans with a client or producer span.kind will have stats computed.
    Enabling this config option may increase the number of spans that generate trace metrics, and may change which spans appear as top-level in Datadog.

  • exporter/datadog: The Datadog exporter now has a config option to identify top-level spans by span kind. This new logic can be enabled by setting traces::compute_top_level_by_span_kind to true in the Datadog exporter config. Default is false. (#​32005)
    traces::compute_top_level_by_span_kind needs to be enabled in both the Datadog connector and Datadog exporter configs if both components are being used.
    With this new logic, root spans and spans with a server or consumer span.kind will be marked as top-level. Additionally, spans with a client or producer span.kind will have stats computed.
    Enabling this config option may increase the number of spans that generate trace metrics, and may change which spans appear as top-level in Datadog.

  • exporter/datadog: Support stable semantic conventions for HTTP spans (#​32823)

  • cmd/opampsupervisor: Persist collector remote config & telemetry settings (#​21078)

  • cmd/opampsupervisor: Support AcceptsRestartCommand Capability. (#​21077)

  • telemetrygen: Add headers to gRPC metadata for logs (#​32668)

  • sshcheckreceiver: Add support for running this receiver on Windows (#​30650)

  • zipkinencodingextension: Move zipkinencodingextension to alpha (#​32702)

🧰 Bug fixes 🧰
  • prometheusremotewrite: Modify prometheusremotewrite.FromMetrics to only generate target_info if there are metrics, as otherwise you can't deduce the timestamp. (#​32318)
  • prometheusremotewrite: Change prometheusremotewrite.FromMetrics so that the target_info metric is only generated if at least one identifying OTel resource attribute (service.name and/or service.instance.id) is defined. (#​32148)
  • k8sclusterreceiver: Fix container state metadata (#​32676)
  • sumologicexporter: do not replace . with _ for prometheus format (#​31479)
  • pkg/stanza: Allow sorting by ascending order when using the mtime sort_type. (#​32792)
  • opampextension: Add a new ppid parameter that can be used to enable orphan detection for the supervisor. (#​32189)
  • awsxrayreceiver: Retain CloudWatch Log Group when translating X-Ray segments (#​31784)
  • pkg/stanza: Fix issue when exclude_older_than is enabled without ordering_criteria configured (#​32681)
  • awskinesisexporter: the compressor was crashing under high load due it not being thread safe. (#​32589)
    removed compressor abstraction and each execution has its own buffer (so it's thread safe)
  • filelogreceiver: When a flush timed out make sure we are at EOF (can't read more) (#​31512, #​32170)
  • vcenterreceiver: Adds the vcenter.cluster.name resource attribute to resource pool with a ClusterComputeResource parent (#​32535)
  • vcenterreceiver: Updates vcenter.cluster.memory.effective (primarily that the value was reporting MiB when it should have been bytes) (#​32782)
  • vcenterreceiver: Adds warning to vcenter.cluster.memory.used metric if configured about its future removal (#​32805)
  • vcenterreceiver: Updates the vcenter.cluster.vm.count metric to also report suspended VM counts (#​32803)
  • vcenterreceiver: Adds vcenter.datacenter.name attributes to all resource types to help with resource identification (#​32531)
  • vcenterreceiver: Adds vcenter.cluster.name attributes warning log related to Datastore resource (#​32674)
  • vcenterreceiver: Adds new vcenter.virtual_app.name and vcenter.virtual_app.inventory_path resource attributes to appropriate VM Resources (#​32557)
  • vcenterreceiver: Adds functionality for vcenter.vm.disk.throughput while also changing to a gauge. (#​32772)
  • vcenterreceiver: Adds initially disabled functionality for VM Templates (#​32821)
  • remotetapprocessor: Fix memory leak on shutdown (#​32571)
  • haproxyreceiver: Fix reading stats larger than 4096 bytes (#​32652)
  • connector/count: Fix handling of non-string attributes in the count connector (#​30314)
  • datadogexporter: Fix nil pointer dereference when using beta infrastructure monitoring offering (#​32865)
    The bug happened under the following conditions:
    • Setting datadog.host.use_as_host_metadata to true on a payload with data about the Datadog exporter host
    • Running using the official opentelemetry-collector-contrib Docker image
  • pkg/translator/jaeger: translate binary attribute values to/from Jaeger as is, without encoding them as base64 strings (#​32204)
  • awscloudwatchreceiver: Fixed a bug where autodiscovery would not use nextToken in the paginated request (#​32053)
  • awsxrayexporter: make comma, as invalid char for x-ray segment name (#​32610)
open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector)

v0.100.0

Compare Source

🛑 Breaking changes 🛑
  • service: The validate sub-command no longer validates that each pipeline's type is the same as its component types (#​10031)
💡 Enhancements 💡
  • semconv: Add support for v1.25.0 semantic convention (#​10072)
  • builder: remove the need to go get a module to address ambiguous import paths (#​10015)
  • pmetric: Support parsing metric.metadata from OTLP JSON. (#​10026)
🧰 Bug fixes 🧰
  • exporterhelper: Fix enabled config option for batch sender (#​10076)

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.

Copy link

coderabbitai bot commented May 6, 2024

Important

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

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 a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @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.

@renovate renovate bot force-pushed the renovate/otel-collector-upstream-dependencies branch from f21adb1 to a2f63c0 Compare May 6, 2024 22:03
@jpkrohling jpkrohling merged commit 8670f02 into main May 7, 2024
1 check passed
@jpkrohling jpkrohling deleted the renovate/otel-collector-upstream-dependencies branch May 7, 2024 06:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant