deps: update dependency jaegertracing/jaeger to v1.48.0 #1542
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.45.0
->v1.48.0
Release Notes
jaegertracing/jaeger (jaegertracing/jaeger)
v1.48.0
: Release 1.48.0Compare Source
Backend Changes
Bug fixes, Minor Improvements
otel trace
spans type to span model (@afzal442 in #4614)OTEL
(@afzal442 in #4599)UI Changes
v1.47.0
: Release 1.47.0Compare Source
1.47.0 (2023-07-05)
Backend Changes
⛔ Breaking Changes
metric names will no longer be normalized by default, meaning that the expected metric names would be
calls
andduration_*
. 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
Bug fixes, Minor Improvements
opentracing.Tracer
to ease migration to OTEL in the future [part 1] (@afzalbin64 in #4529)redis
service to use native OTEL instrumentation (@afzal442 in #4533)UI Changes
v1.46.0
Compare Source
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 tofalse
if OTLP receiver is not desired.New Features
Bug fixes, Minor Improvements
Maintenance
UI Changes
UI pinned to version 1.30.0. New features:
Configuration
📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" in timezone Europe/Vienna, 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 this update again.
This PR has been generated by Mend Renovate. View repository job log here.