chore(deps): update dependency github.com/grafana/tempo/operations/tempo-mixin to v2.7.0 #686
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:
v2.6.1
->v2.7.0
Release Notes
grafana/tempo (github.com/grafana/tempo/operations/tempo-mixin)
v2.7.0
Compare Source
If you would like to re-enable it, we recommend 'snappy'. Use the following settings:
request cancellations are exposed under
result
label intempo_query_frontend_queries_total
andtempo_query_frontend_queries_within_slo_total
withcompleted
orcanceled
values to differentiate between completed and canceled requests.BREAKING CHANGE The
tempo-cli
now uses the/api/v2/traces
endpoint by default,please use
--v1
flag to use/api/traces
endpoint, which was the default in previous versions.use_otel_tracer
configuration option. Use the OpenTelemetry environment variables to configure the span exporter #4028,#3646 (@andreasgerstmayr)To continue using the Jaeger exporter, use the following environment variable:
OTEL_TRACES_EXPORTER=jaeger
.BREAKING CHANGE After this update the Open-Telemetry Collector receiver will connect to
localhost
instead of all interfaces0.0.0.0
.Due to this, Tempo installations running inside Docker have to update the address they listen.
For more details on this change, see #4465
For more information about the security risk this change addresses, see https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/security-best-practices.md#safeguards-against-denial-of-service-attacks
cespare/xxhash
withcespare/xxhash/v2
#4485 (@Juneezee)log_discarded_spans
#3957 (@dastrobu)max_spans_per_span_set
to 0 to obtain the old behavior. #4275 (@carles-grafana)BREAKING CHANGE Removed
querier_forget_delay
setting from the frontend. This configuration option did nothing.insecure-skip-verify
option in tempo-cli to skip SSL certificate validation when connecting to the S3 backend. #4259 (@faridtmammadov)invalid_utf8
to reasons spanmetrics will discard spans. #4293 (@zalegrala)Added tunable prealloc env vars PREALLOC_BKT_SIZE, PREALLOC_NUM_BUCKETS, PREALLOC_MIN_BUCKET and metric tempo_ingester_prealloc_miss_bytes_total to observe and tune prealloc behavior.
BREAKING CHANGE All regular expression matchers will now be fully anchored.
span.foo =~ "bar"
will now be evaluated asspan.foo =~ "^bar$"
This will cause the ingester to more aggressively and correctly refuse traces. Also added two metrics to better track bytes consumed per tenant in the ingester.
tempo_metrics_generator_live_trace_bytes
andtempo_ingester_live_trace_bytes
.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 this update again.
This PR was generated by Mend Renovate. View the repository job log.