chore(deps): update dependency tempo to v2.9.0 #815
Merged
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.8.2->v2.9.0Release Notes
grafana/tempo (tempo)
v2.9.0Compare Source
tempo_metrics_generator_processor_service_graphs_expired_edgesto exclude edges that are counted in the service graph. #5319 (@joe-elliott)tempo-cli analyse block(s) excludes attributes with array values. #5380 (@stoewer)This also changes the TraceQL metrics responses of
/api/metrics/query_rangeand/api/metrics/queryto remove the redundantprom_labelsfield which was the error source. There may be an interruption to TraceQL metrics queries during rollout while components are running the previous version. #5659 (@mdisibio)sample=trueandsample=0.xxwhich can speed up TraceQL metrics queries by sampling a subset of the data to provide an approximate result. #5469 (@mdisibio)query_frontend_bytes_inspected_total, which shows the total number of bytes read from disk and object storage #5310 (@carles-grafana)spans_distance_in_future_seconds/spans_distance_in_past_secondsthat count spans with end timestamp in the future / past. While spans in the future are accepted, they are invalid and may not be found using the Search API. #4936 (@carles-grafana)db.namespaceattribute for service-graph DB nodes. #5602 (@gouthamve)compare()performance improvement. #5419 (@mdisibio)spanmetricsprocessor. #5122 (@KyriosGN0)quantile_over_time(). #5278 (@zalegrala)tempo_distributor_ingress_bytes_total. #5601 (@mapno)/status/runtime_configendpoint by adding document separator. #5371 (@iamrajiv)query_rangeHTTP handling that could be triggered by cancellations or other errors. #5667 (@mdisibio)api/v2/search/tags. (SearchTagsV2) #5607 (@ruslan-mikhailov)4319→4317). #5536SearchTagValuesV2endpoint. #5493 (@carles-grafana)v2.9-rc.0 Tempo Rearchitecture [EXPERIMENTAL]
backend_scheduler.tenant_measurement_interval, usebackend_scheduler.compaction.measure_intervalinstead. #5328 (@zalegrala)min/maxinput blocks for compaction provider. #5373 (@zalegrala)The configuration for
backend_scheduler.provider.compaction.backoffhas been removed.Additionally, the
compaction_tenant_backoff_totalmetric has been renamed tocompaction_empty_tenant_cycle_totalfor clarity.30sby default. #5460 (@zalegrala)listOffsetby partition client. #5415 (@javiermolinar)jsonnetlib. #5591 #5606 #5609 (@mapno)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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 Renovate Bot.