[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)
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.
[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)
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.
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)
You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/stripe/veneur/network/alerts).
Bumps github.com/jaegertracing/jaeger from 1.15.1 to 1.47.0.
Release notes
Sourced from github.com/jaegertracing/jaeger's releases.
... (truncated)
Changelog
Sourced from github.com/jaegertracing/jaeger's changelog.
... (truncated)
Commits
ee6cc41[hotrod] Handle both OT and OTEL baggage (#4572)10b7fe3Prepare release v1.47.0 (#4570)0b21373[tracegen] Enable OTEL debug logging (#4571)2915652Bump golang.org/x/net from 0.11.0 to 0.12.0 (#4569)22ebec3Bump the otel-collector group with 1 update (#4568)1b28b23Bump golang.org/x/sys from 0.9.0 to 0.10.0 (#4564)c3aaa98Bump step-security/harden-runner from 2.4.0 to 2.4.1 (#4551)d331476Bump the hashicorp group with 1 update (#4562)3775639Bump the otel-collector group with 2 updates (#4563)3a67259Reduce dependabot pattern to 50 charsDependabot 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) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/stripe/veneur/network/alerts).