jaegertracing / jaeger-opentelemetry-collector

Experimental: components needed to build Jaeger on top of OpenTelemetry Collector
https://github.com/jaegertracing/jaeger
Apache License 2.0
12 stars 7 forks source link

Bump github.com/open-telemetry/opentelemetry-collector-contrib/receiver/zipkinreceiver from 0.59.0 to 0.79.0 #194

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps github.com/open-telemetry/opentelemetry-collector-contrib/receiver/zipkinreceiver from 0.59.0 to 0.79.0.

Release notes

Sourced from github.com/open-telemetry/opentelemetry-collector-contrib/receiver/zipkinreceiver's releases.

v0.79.0

The OpenTelemetry Collector Contrib contains everything in the opentelemetry-collector release, be sure to check the release notes there as well.

šŸ›‘ Breaking changes šŸ›‘

  • attributesprocessor: Enable SHA-256 as hashing algorithm by default for attributesprocessor hashing action (#4759)
  • windowseventlogreceiver: Emit raw Windows events as strings instead of byte arrays (#22704)
  • receiver/httpcheck: Removed the default endpoint value of http://localhost:80. The endpoint property is now required. (#22995)
  • pkg/ottl: Removes StandardTypeGetter in favor of StandardStringGetter, StandardIntGetter, StandardFloatGetter, and StandardPMapGetter, which handle converting pcommon.Values of the proper type. (#22763) This is only a breaking change for users using OTTL in custom components. For all Contrib components this is an enhancement.
  • postgresqlreceiver: Remove resource attribute feature gates (#22479)

šŸš© Deprecations šŸš©

  • dockerstatsreceiver: cpu.container.percent metric will be deprecated in v0.79.0 in favor of container.cpu.utilization (#21807) This starts the process of phasing out incorrect metric name:
    • container.cpu.utilization and replacing it with the names adhering to the semantic conventions:
    • container.cpu.percent At this stage, the new metric is added, but is disabled by default. See the "Deprecations" section of the Docker Stats receiver's README for details.

šŸ’” Enhancements šŸ’”

  • receiver/azuremonitorreceiver: Retrieve metric values with all dimension keys in filter (#21715)
  • apachesparkreceiver: Changes required to move the Apache Spark receiver to Alpha stability (#21046)
  • journaldreceiver: add support for grep (#20295)
  • mysqlreceiver: add mysql.uptime metric (#14138)
  • googlecloudspannerreceiver: Adding a new config option to allow truncation of query text to 1024 characters. (#22072)
  • vcenterreceiver: Adds VM memory utilisation metric (#20917)
  • receivers: Adding initial_delay to receivers to control when scraping interval starts (#23030) The updated receivers are:
    • active_directory_ds
    • aerospike
    • apache
    • apachespark
    • azuremonitor
    • couchdb
    • chrony
    • docker_stats
    • elasticsearch
    • expvar
    • filestats
    • flinkmetrics
    • googlecloudspanner
    • haproxy
    • httpcheck
    • iis
    • memcached

... (truncated)

Changelog

Sourced from github.com/open-telemetry/opentelemetry-collector-contrib/receiver/zipkinreceiver's changelog.

v0.79.0

šŸ›‘ Breaking changes šŸ›‘

  • attributesprocessor: Enable SHA-256 as hashing algorithm by default for attributesprocessor hashing action (#4759)
  • windowseventlogreceiver: Emit raw Windows events as strings instead of byte arrays (#22704)
  • receiver/httpcheck: Removed the default endpoint value of http://localhost:80. The endpoint property is now required. (#22995)
  • pkg/ottl: Removes StandardTypeGetter in favor of StandardStringGetter, StandardIntGetter, StandardFloatGetter, and StandardPMapGetter, which handle converting pcommon.Values of the proper type. (#22763) This is only a breaking change for users using OTTL in custom components. For all Contrib components this is an enhancement.
  • postgresqlreceiver: Remove resource attribute feature gates (#22479)

šŸš© Deprecations šŸš©

  • dockerstatsreceiver: cpu.container.percent metric will be deprecated in v0.79.0 in favor of container.cpu.utilization (#21807) This starts the process of phasing out incorrect metric name:
    • container.cpu.utilization and replacing it with the names adhering to the semantic conventions:
    • container.cpu.percent At this stage, the new metric is added, but is disabled by default. See the "Deprecations" section of the Docker Stats receiver's README for details.

šŸ’” Enhancements šŸ’”

  • receiver/azuremonitorreceiver: Retrieve metric values with all dimension keys in filter (#21715)
  • apachesparkreceiver: Changes required to move the Apache Spark receiver to Alpha stability (#21046)
  • journaldreceiver: add support for grep (#20295)
  • mysqlreceiver: add mysql.uptime metric (#14138)
  • googlecloudspannerreceiver: Adding a new config option to allow truncation of query text to 1024 characters. (#22072)
  • vcenterreceiver: Adds VM memory utilisation metric (#20917)
  • receivers: Adding initial_delay to receivers to control when scraping interval starts (#23030) The updated receivers are:
    • active_directory_ds
    • aerospike
    • apache
    • apachespark
    • azuremonitor
    • couchdb
    • chrony
    • docker_stats
    • elasticsearch
    • expvar
    • filestats
    • flinkmetrics
    • googlecloudspanner
    • haproxy
    • httpcheck
    • iis
    • memcached
    • mongodb

... (truncated)

Commits
  • 82e8c13 [chore] Prepare release 0.79.0 (#23185)
  • d12164d [chore] update core to 0.79.0 (#23180)
  • b088ba8 [exporter/datadog] Use v0.3.0 of opentelemetry-mapping-go for logs (#23137)
  • 4a0ea8e [chore] Improving life cycle tests reporting (#23145)
  • 24dceab [chore] [receiver/k8scluster] Fix links in containers.go (#23148)
  • fd0c6ff [bugfix][jmxreceiver] Cancel rogue subprocess (#23051)
  • e4c3488 [chore] Fix failing test case for flinkmetrics (#23143)
  • 4ed6328 [chore] [receiver/filelog] Add test to verify receiver consume contract (#22833)
  • a8c03d0 [pkg/ottl] Added ottl functions for hashing strings (#22968)
  • dc90ec9 [pkg/stanza/fileconsumer] Fix issue where empty files caused errors (#22945)
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 1 year ago

Superseded by #200.