Bump github.com/jaegertracing/jaeger from 1.41.0 to 1.47.0 in /exporter/jaegerthrifthttpexporter

[dependabot]

Bumps github.com/jaegertracing/jaeger from 1.41.0 to 1.47.0.

Release notes

Sourced from github.com/jaegertracing/jaeger's releases.

Release 1.47.0

1.47.0 (2023-07-05)

Backend Changes

⛔ Breaking Changes

• [SPM] Due to a breaking change in OpenTelemetry's prometheus exporter (details) metric names will no longer be normalized by default, meaning that the expected metric names would be calls and duration_*. Backwards compatibility with older OpenTelemetry Collector versions can be achieved through the following flags:
  • prometheus.query.normalize-calls: If true, normalizes the "calls" metric name. e.g. "calls_total".
  • prometheus.query.normalize-duration: If true, normalizes the "duration" metric name to include the duration units. e.g. "duration_milliseconds_bucket".

New Features

• [Cassandra] Add Configuration.Close() to ensure TLS cert watcher is closed (@​kennyaz in #4515)
• Add *.kerberos.disable-fast-negotiation option to Kafka consumer (@​pmuls99 in #4520)
• Support Prometheus normalization for specific metrics related to OpenTelemetry compatibility (@​albertteoh in #4555)

Bug fixes, Minor Improvements

• Add readme for memstore plugin (@​yurishkuro in 283bdd9)
• Pass a wrapper instead of opentracing.Tracer to ease migration to OTEL in the future [part 1] (@​afzalbin64 in #4529)
• [hotROD] Add OTEL instrumentation to customer svc (@​afzal442 in #4559)
• [hotROD] Replace gRPC instrumentation with OTEL (@​afzal442 in #4558)
• [hotROD]: Upgrade redis service to use native OTEL instrumentation (@​afzal442 in #4533)
• [hotROD] Fix OTEL logging in HotRod example (@​albertteoh in #4556)
• [hotrod] Reduce span exporter's batch timeout to let the spans be exported sooner (@​GLVSKiriti in #4518)
• [tracegen] Add options to generate more spans and attributes for additional use cases (@​yurishkuro in #4535)
• Build improvement to rebuild jaeger-ui if the tree does not match any tag (@​bobrik in #4553)
• [Test] Fixed a race condition causing unit test failure by changing the logging (@​yurishkuro in #4546) resolves #4497

UI Changes

• UI pinned to version 1.31.0.

Release v1.46.0

Backend Changes

⛔ Breaking Changes

OTLP receiver is now enabled by default (#4494). This change follows the Jaeger's strategic direction of aligning closely with the OpenTelemetry project. This may cause port conflicts if jaeger-collector is depoyed in host network namespace. The original --collector.otlp.enabled option is still available and MUST be set to false if OTLP receiver is not desired.

New Features

• Make OTLP receiver enabled by default (@​yurishkuro in #4494)
• [SPM] Add support for OpenTelemetry SpanMetrics Connector (@​albertteoh in #4452). See Migration README.

Bug fixes, Minor Improvements

... (truncated)

Changelog

Sourced from github.com/jaegertracing/jaeger's changelog.

1.47.0 (2023-07-05)

Backend Changes

⛔ Breaking Changes

• [SPM] Due to a breaking change in OpenTelemetry's prometheus exporter (details) metric names will no longer be normalized by default, meaning that the expected metric names would be calls and duration_*. Backwards compatibility with older OpenTelemetry Collector versions can be achieved through the following flags:
  • prometheus.query.normalize-calls: If true, normalizes the "calls" metric name. e.g. "calls_total".
  • prometheus.query.normalize-duration: If true, normalizes the "duration" metric name to include the duration units. e.g. "duration_milliseconds_bucket".

New Features

• [Cassandra] Add Configuration.Close() to ensure TLS cert watcher is closed (@​kennyaz in #4515)
• Add *.kerberos.disable-fast-negotiation option to Kafka consumer (@​pmuls99 in #4520)
• Support Prometheus normalization for specific metrics related to OpenTelemetry compatibility (@​albertteoh in #4555)

Bug fixes, Minor Improvements

• Add readme for memstore plugin (@​yurishkuro in 283bdd9)
• Pass a wrapper instead of opentracing.Tracer to ease migration to OTEL in the future [part 1] (@​afzalbin64 in #4529)
• [hotROD] Add OTEL instrumentation to customer svc (@​afzal442 in #4559)
• [hotROD] Replace gRPC instrumentation with OTEL (@​afzal442 in #4558)
• [hotROD]: Upgrade redis service to use native OTEL instrumentation (@​afzal442 in #4533)
• [hotROD] Fix OTEL logging in HotRod example (@​albertteoh in #4556)
• [hotrod] Reduce span exporter's batch timeout to let the spans be exported sooner (@​GLVSKiriti in #4518)
• [tracegen] Add options to generate more spans and attributes for additional use cases (@​yurishkuro in #4535)
• Build improvement to rebuild jaeger-ui if the tree does not match any tag (@​bobrik in #4553)
• [Test] Fixed a race condition causing unit test failure by changing the logging (@​yurishkuro in #4546) resolves #4497

UI Changes

• UI pinned to version 1.31.0.

1.46.0 (2023-06-05)

Backend Changes

⛔ Breaking Changes

OTLP receiver is now enabled by default (#4494). This change follows the Jaeger's strategic direction of aligning closely with the OpenTelemetry project. This may cause port conflicts if jaeger-collector is depoyed in host network namespace. The original --collector.otlp.enabled option is still available and MUST be set to false if OTLP receiver is not desired.

New Features

• Make OTLP receiver enabled by default (@​yurishkuro in #4494)
• [SPM] Add support for OpenTelemetry SpanMetrics Connector (@​albertteoh in #4452). See Migration README.

Bug fixes, Minor Improvements

... (truncated)

Commits

• ee6cc41 [hotrod] Handle both OT and OTEL baggage (#4572)
• 10b7fe3 Prepare release v1.47.0 (#4570)
• 0b21373 [tracegen] Enable OTEL debug logging (#4571)
• 2915652 Bump golang.org/x/net from 0.11.0 to 0.12.0 (#4569)
• 22ebec3 Bump the otel-collector group with 1 update (#4568)
• 1b28b23 Bump golang.org/x/sys from 0.9.0 to 0.10.0 (#4564)
• c3aaa98 Bump step-security/harden-runner from 2.4.0 to 2.4.1 (#4551)
• d331476 Bump the hashicorp group with 1 update (#4562)
• 3775639 Bump the otel-collector group with 2 updates (#4563)
• 3a67259 Reduce dependabot pattern to 50 chars
• Additional commits viewable in compare view

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)

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[github-actions]

Closed as inactive. Feel free to reopen if this PR is still being worked on.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.