Grafana Mimir provides horizontally scalable, highly available, multi-tenant, long-term storage for Prometheus.
This release contains 5 PRs from 3 authors. Thank you!
golang.org/x/net
to 0.17
, which include fix for CVE-2023-44487. #6353 #6364All changes in this release: https://github.com/grafana/mimir/compare/mimir-2.9.1...mimir-2.9.2
This release contains 2 PRs from 1 authors. Thank you!
This release contains a known bug in the grpc-go
library that drastically affects network performance of the servers.
Mimir 2.10.3 was released fixing this issue.
golang.org/x/net
to 0.17
, which include fix for CVE-2023-44487. #6349All changes in this release: https://github.com/grafana/mimir/compare/mimir-2.10.1...mimir-2.10.2
This release contains 6 PRs from 4 authors. Thank you!
All changes in this release: https://github.com/grafana/mimir/compare/mimir-2.10.0...mimir-2.10.1
This release contains 455 PRs from 54 authors, including new contributors Aaron Sanders, Alexander Proschek, Aljoscha Pörtner, balazs92117, Francois Gouteroux, Franco Posa, Heather Yuan, jingyang, kendrickclark, m4r1u2, Milan Plžík, Samir Teymurov, Sven Haardiek, Thomas Schaaf, Tiago Posse. Thank you!
Grafana Labs is excited to announce version 2.10 of Grafana Mimir.
The highlights that follow include the top features, enhancements, and bugfixes in this release. For the complete list of changes, see the changelog.
file
, ruler_group
and rule_name
parameters to the ruler endpoint /api/v1/rules
./api/v1/cardinality/label_values
by passing the count_method
parameter. You can set it to active
to count only series that are considered active according to the -ingester.active-series-metrics-idle-timeout
flag setting rather than counting all in-memory series.-log.buffered
CLI flag. This should reduce contention and resource usage under heavy usage patterns.__name__
posting group causing a reduction in the number of object storage API calls.Mimir
and the Version
set correctly in order to benefit from this improvement.-query-frontend.cache-results
is enabled, and -query-frontend.results-cache-ttl-for-cardinality-query
or -query-frontend.results-cache-ttl-for-labels-query
is set to a value greater than 0.-compactor.no-blocks-file-cleanup-enabled
option to true
./ingester/tenants
and /ingester/tsdb/{tenant}
to the ingester that provide debug information about tenants and their TSDBs.cortex_ingester_active_native_histogram_series
, cortex_ingester_active_native_histogram_series_custom_tracker
, cortex_ingester_active_native_histogram_buckets
, cortex_ingester_active_native_histogram_buckets_custom_tracker
. The first 2 are the subsets of the existing and unmodified cortex_ingester_active_series
and cortex_ingester_active_series_custom_tracker
respectively, only tracking native histogram series, and the last 2 are the equivalent for tracking the number of buckets in native histogram series.Additionally, the following previously experimental features are now considered stable:
-ruler-storage.cache.*
CLI flags or their respective YAML config options.-query-frontend.query-sharding-target-series-per-shard
; we recommend starting with a value of 2500
.-query-frontend.max-query-expression-size-bytes
.-overrides-exporter.ring.enabled
.-overrides-exporter.enabled-metrics
.results_cache_ttl
and results_cache_ttl_for_out_of_order_time_window
parameters.Grafana Mimir 2.10 includes new features that are considered as experimental and disabled by default. Please use them with caution and report any issues you encounter:
-blocks-storage.bucket-store.index-header-sparse-persistence-enabled
) as well as the ability to persist the list of block IDs that were lazy-loaded while running to eagerly load them upon startup to prevent starting up with no loaded blocks (-blocks-storage.bucket-store.index-header.eager-loading-startup-enabled
) and an option to limit the number of concurrent index-header loads when lazy-loading (-blocks-storage.bucket-store.index-header-lazy-loading-concurrency
).-querier.minimize-ingester-requests
).-blocks-storage.tsdb.early-head-compaction-min-in-memory-series
).-querier.prefer-streaming-chunks-from-store-gateways
option.-ingester.client.circuit-breaker.*
configuration options and should serve to let ingesters recover when under high pressure.-ingester.read-path-cpu-utilization-limit
, -ingester.read-path-memory-utilization-limit
, -ingester.log-utilization-based-limiter-cpu-samples
).The Grafana Mimir and Grafana Enterprise Metrics Helm chart is now released independently. See the Grafana Mimir Helm chart documentation.
In Grafana Mimir 2.10 we have changed the following behaviors:
ACTIVE
state in the ring. This is not expected to introduce any degradation in terms of query results correctness or high-availability.cortex_distributor_instance_rejected_requests_total
cortex_ingester_instance_rejected_requests_total
-validation.create-grace-period
is now enforced in the ingester. If you've configured -validation.create-grace-period
, make sure the configuration is applied to ingesters too.-validation.create-grace-period
is now enforced for exemplars. The cortex_discarded_exemplars_total{reason="exemplar_too_far_in_future",user="..."}
series is incremented when exemplars are dropped because their timestamp is greater than "now + grace_period".-validation.create-grace-period
is now enforced in the query-frontend even when the configured value is 0. When the value is 0, the query end time range is truncated to the current real-world time.The following metrics were removed:
cortex_ingester_shipper_dir_syncs_total
cortex_ingester_shipper_dir_sync_failures_total
The following configuration options are deprecated and will be removed in Grafana Mimir 2.12:
-blocks-storage.bucket-store.index-header-lazy-loading-enabled
is deprecated, use the new configuration -blocks-storage.bucket-store.index-header.lazy-loading-enabled
.-blocks-storage.bucket-store.index-header-lazy-loading-idle-timeout
is deprecated, use the new configuration -blocks-storage.bucket-store.index-header.lazy-loading-idle-timeout
.-blocks-storage.bucket-store.index-header-lazy-loading-concurrency
is deprecated, use the new configuration -blocks-storage.bucket-store.index-header.lazy-loading-concurrency
.The following configuration options that were deprecated in Grafana Mimir 2.8 are removed:
blocks-storage.tsdb.max-tsdb-opening-concurrency-on-startup
.The following experimental configuration options were renamed or removed:
-querier.prefer-streaming-chunks
was renamed to -querier.prefer-streaming-chunks-from-ingesters
.-blocks-storage.bucket-store.chunks-cache.fine-grained-chunks-caching-enabled
was removed.-blocks-storage.bucket-store.fine-grained-chunks-caching-ranges-per-series
was removed.The following experimental options are now stable:
-shutdown-delay
.-ingester.ring.excluded-zones
.The following configuration option defaults were changed:
-querier.streaming-chunks-per-ingester-buffer-size
was changed from 512
to 256
.5s
(default inherited from gRPC client was 20s
) with a default max backoff delay of 5s
(default inherited from gRPC client was 120s
).LEAVING
and the number of tokens has changed upon restarting.timestamp()
function fail with execution: attempted to read series at index 0 from stream, but the stream has already been exhausted
if the experimental feature to stream chunks from ingesters to queriers is enabled.memberlist_client_kv_store_count
metric that used to exist in Cortex, but got lost during grafana/dskit updates before Mimir 2.0.blocks_storage.bucket_store.index_header.verify_on_load: true
. #5174-querier.streaming-chunks-per-ingester-buffer-size
flag to 256. #5203ACTIVE
state in the ring. #5342-querier.prefer-streaming-chunks
to -querier.prefer-streaming-chunks-from-ingesters
to enable streaming chunks from ingesters to queriers. #5182-query-frontend.cache-unaligned-requests
has been moved from a global flag to a per-tenant override. #5312cortex_ingester_shipper_dir_syncs_total
and cortex_ingester_shipper_dir_sync_failures_total
metrics. The former metric was not much useful, and the latter was never incremented. #5396-validation.create-grace-period
is now enforced in the ingester too, other than distributor and query-frontend. If you've configured -validation.create-grace-period
then make sure the configuration is applied to ingesters too. #5712-validation.create-grace-period
is now enforced for examplars too in the distributor. If an examplar has timestamp greater than "now + grace_period", then the exemplar will be dropped and the metric cortex_discarded_exemplars_total{reason="exemplar_too_far_in_future",user="..."}
increased. #5761-validation.create-grace-period
is now enforced in the query-frontend even when the configured value is 0. When the value is 0, the query end time range is truncated to the current real-world time. #5829blocks-storage.bucket-store
and use a new configurations in blocks-storage.bucket-store.index-header
, deprecated configuration will be removed in Mimir 2.12. Configuration changes: #5726
-blocks-storage.bucket-store.index-header-lazy-loading-enabled
is deprecated, use the new configuration -blocks-storage.bucket-store.index-header.lazy-loading-enabled
-blocks-storage.bucket-store.index-header-lazy-loading-idle-timeout
is deprecated, use the new configuration -blocks-storage.bucket-store.index-header.lazy-loading-idle-timeout
-blocks-storage.bucket-store.index-header-lazy-loading-concurrency
is deprecated, use the new configuration -blocks-storage.bucket-store.index-header.lazy-loading-concurrency
-blocks-storage.bucket-store.chunks-cache.fine-grained-chunks-caching-enabled
, -blocks-storage.bucket-store.fine-grained-chunks-caching-ranges-per-series
. #5816 #5875blocks-storage.tsdb.max-tsdb-opening-concurrency-on-startup
. #5850-distributor.service-overload-status-code-on-rate-limit-enabled
flag for configuring status code to 529 instead of 429 upon rate limit exhaustion. #5752count_method
parameter which enables counting active series. #5136-query-frontend.cache-results
is enabled, and -query-frontend.results-cache-ttl-for-cardinality-query
or -query-frontend.results-cache-ttl-for-labels-query
set to a value greater than 0. The following metrics have been added to track the query results cache hit ratio per request_type
: #5212 #5235 #5426 #5524
cortex_frontend_query_result_cache_requests_total{request_type="query_range|cardinality|label_names_and_values"}
cortex_frontend_query_result_cache_hits_total{request_type="query_range|cardinality|label_names_and_values"}
-<prefix>.s3.list-objects-version
flag to configure the S3 list objects version. #5099-ingester.read-path-cpu-utilization-limit
-ingester.read-path-memory-utilization-limit
-ingester.log-utilization-based-limiter-cpu-samples
file
, rule_group
and rule_name
. #5291-ingester.ring.token-generation-strategy: spread-minimizing
and -ingester.ring.spread-minimizing-zones: <all available zones>
. In that case -ingester.ring.tokens-file-path
must be empty. #5308 #5324-ingester.ring.spread-minimizing-join-ring-in-order
that allows an ingester to register tokens in the ring only after all previous ingesters (with ID lower than its own ID) have already been registered. #5541-blocks-storage.tsdb.early-head-compaction-min-in-memory-series
, and the ingester estimates that the per-tenant TSDB Head compaction will reduce in-memory series by at least -blocks-storage.tsdb.early-head-compaction-min-estimated-series-reduction-percentage
. #5371cortex_ingester_active_native_histogram_series
, cortex_ingester_active_native_histogram_series_custom_tracker
, cortex_ingester_active_native_histogram_buckets
, cortex_ingester_active_native_histogram_buckets_custom_tracker
. The first 2 are the subsets of the existing and unmodified cortex_ingester_active_series
and cortex_ingester_active_series_custom_tracker
respectively, only tracking native histogram series, and the last 2 are the equivalents for tracking the number of buckets in native histogram series. #5318-<prefix>.s3.native-aws-auth-enabled
that allows to enable the default credentials provider chain of the AWS SDK. #5636-ingester.client.circuit-breaker.enabled
, -ingester.client.circuit-breaker.failure-threshold
, or -ingester.client.circuit-breaker.cooldown-period
or their corresponding YAML. #5650-ruler-storage.cache.*
)-ingester.ring.excluded-zones
)-query-frontend.query-sharding-target-series-per-shard
)-query-frontend.results-cache-ttl-for-cardinality-query
)-query-frontend.results-cache-ttl-for-labels-query
)-query-frontend.max-query-expression-size-bytes
)-overrides-exporter.ring.enabled
)-overrides-exporter.enabled-metrics
)-query-frontend.results-cache-ttl
, -query-frontend.results-cache-ttl-for-out-of-order-time-window
)-shutdown-delay
)-tenant-federation.max-concurrent
to adjust the max number of per-tenant queries that can be run at a time when executing a single multi-tenant query. #5874max_global_metadata_per_user
, max_global_metadata_per_metric
, request_rate
, request_burst_size
, alertmanager_notification_rate_limit
, alertmanager_max_dispatcher_aggregation_groups
, alertmanager_max_alerts_count
, alertmanager_max_alerts_size_bytes
) and added flag -overrides-exporter.enabled-metrics
to explicitly configure desired metrics, e.g. -overrides-exporter.enabled-metrics=request_rate,ingestion_rate
. Default value for this flag is: ingestion_rate,ingestion_burst_size,max_global_series_per_user,max_global_series_per_metric,max_global_exemplars_per_user,max_fetched_chunks_per_query,max_fetched_series_per_query,ruler_max_rules_per_rule_group,ruler_max_rule_groups_per_tenant
. #5376-timeseries-unmarshal-caching-optimization-enabled=false
. #5137-<prefix>.connect-timeout
-<prefix>.connect-backoff-base-delay
-<prefix>.connect-backoff-max-delay
-<prefix>.initial-stream-window-size
-<prefix>.initial-connection-window-size
-distributor.write-requests-buffer-pooling-enabled
to true
. #5195 #5805 #5830-querier.minimize-ingester-requests
option to initially query only the minimum set of ingesters required to reach quorum. #5202 #5259 #5263cortex_ruler_sync_rules_duration_seconds
metric, tracking the time spent syncing all rule groups owned by the ruler instance. #5311blocks-storage.bucket-store.index-header-lazy-loading-concurrency
config option to limit the number of concurrent index-headers loads when lazy loading. #5313 #5605cortex_querier_queries_rejected_total
metric that counts the number of queries rejected due to hitting a limit (eg. max series per query or max chunks per query). #5316 #5440 #5450-querier.minimize-ingester-requests-hedging-delay
option to initiate requests to further ingesters when request minimisation is enabled and not all initial requests have completed. #5368-ingester.client.*
flags to make it clear that these are used by both queriers and distributors. #5375-querier.prefer-streaming-chunks-from-store-gateways=true
. #5182max-chunks-per-query
limit earlier in query processing when streaming chunks from ingesters to queriers to avoid unnecessarily consuming resources for queries that will be aborted. #5369 #5447cortex_ingester_shipper_last_successful_upload_timestamp_seconds
metric tracking the last successful TSDB block uploaded to the bucket (unix timestamp in seconds). #5396cortex_ingester_utilization_limiter_current_cpu_load
: The current exponential weighted moving average of the ingester's CPU loadcortex_ingester_utilization_limiter_current_memory_usage_bytes
: The current ingester memory utilizationinsight=true
field to ruler's prometheus component for rule evaluation logs. #5510cortex_distributor_instance_rejected_requests_total
and cortex_ingester_instance_rejected_requests_total
respectively. #5551-log.buffered
CLI flag enable buffered logging.-compactor.no-blocks-file-cleanup-enabled
option. #5648-store-gateway.sharding-ring.auto-forget-enabled
configuration parameter to control whether store-gateway auto-forget feature should be enabled or disabled (enabled by default). #5702cortex_block_upload_api_blocks_total
, cortex_block_upload_api_bytes_total
, and cortex_block_upload_api_files_total
. #5738-log.rate-limit-enabled
-log.rate-limit-logs-per-second
-log.rate-limit-logs-per-second-burst
cortex_ingester_tsdb_head_min_timestamp_seconds
and cortex_ingester_tsdb_head_max_timestamp_seconds
metrics which return min and max time of all TSDB Heads open in an ingester. #5786 #5815-querier.max-estimated-fetched-chunks-per-query-multiplier
. #5765__name__
posting group in selection in order to reduce the number of object storage API calls. #5246timestamp()
function fail with execution: attempted to read series at index 0 from stream, but the stream has already been exhausted
if streaming chunks from ingesters to queriers is enabled. #5370memberlist_client_kv_store_count
metric that used to exist in Cortex, but got lost during dskit updates before Mimir 2.0. #5377cortex_ingester_client_request_duration_seconds
metric did not include streaming query requests that did not return any series. #5695not found
errors on label values API during head compaction. #5957MimirProvisioningTooManyActiveSeries
alert. You should configure -ingester.instance-limits.max-series
and rely on MimirIngesterReachingSeriesLimit
alert instead. #5593MimirProvisioningTooManyWrites
alert. The alerting threshold used in this alert was chosen arbitrarily and ingesters receiving an higher number of samples / sec don't necessarily have any issue. You should rely on SLOs metrics and alerts instead. #5706MimirRequestErrors
or MimirRequestLatency
alert for the /debug/pprof
endpoint. #5826MimirIngestedDataTooFarInTheFuture
warning alert that triggers when Mimir ingests sample with timestamp more than 1h in the future. #5822MimirIngesterRestarts
to fire only when the ingester container is restarted, excluding the cases the pod is rescheduled. #5397MimirIngesterHasNotShippedBlocks
and MimirIngesterHasNotShippedBlocksSinceStart
alerts. #5396MimirGossipMembersMismatch
to include admin-api
and custom compactor pods. admin-api
is a GEM component. #5641 #5797_config.querier.concurrency
configuration option and replaced it with _config.querier_max_concurrency
and _config.ruler_querier_max_concurrency
to allow to easily fine tune it for different querier deployments. #5322_config.multi_zone_ingester_max_unavailable
to 50. #5327maxSurge
and maxUnavailable
are set to 15%
and 0
. #5714autoscaling_alertmanager_enabled: true
. #5194 #5249track_sizes
feature for Memcached pods to help determine cache efficiency. #5209PodDisruptionBudget
s for compactor, continuous-test, distributor, overrides-exporter, querier, query-frontend, query-scheduler, rollout-operator, ruler, ruler-querier, ruler-query-frontend, ruler-query-scheduler, and all memcached workloads. #5098_config.shuffle_sharding.target_series_per_ingester
and _config.shuffle_sharding.target_utilization_percentage
values. #5470_config.autoscaling_distributor_cpu_target_utilization
. #5525_config.ruler_remote_evaluation_max_query_response_size_bytes
to easily set the maximum query response size allowed (in bytes). #5592GOMAXPROCS
based on the CPU request. This should reduce distributor CPU utilization, assuming the CPU request is set to a value close to the actual utilization. #5588GOMAXPROCS
based on the CPU request. This should reduce noisy neighbour issues created by the querier, whose CPU utilization could eventually saturate the Kubernetes node if unbounded. #5646 #5658null
in the *_env_map
objects (e.g. store_gateway_env_map+:: { 'field': null}
). #5599etcd
. #5589autoscaling_querier_target_utilization
(defaults to 0.75
)autoscaling_mimir_read_target_utilization
(defaults to 0.75
)autoscaling_ruler_querier_cpu_target_utilization
(defaults to 1
)autoscaling_distributor_memory_target_utilization
(defaults to 1
)autoscaling_ruler_cpu_target_utilization
(defaults to 1
)autoscaling_query_frontend_cpu_target_utilization
(defaults to 1
)autoscaling_ruler_query_frontend_cpu_target_utilization
(defaults to 1
)autoscaling_alertmanager_cpu_target_utilization
(defaults to 1
)v0.7.0
. #5718mimirtool analyse grafana
. This allows the tool to work correctly when running against Grafana instances with more than a 1000 dashboards. #5825__name__
matcher. #5911label_values(<label_name>)
when running mimirtool analyse grafana
. #5832Content-Type
response header from backend. Previously Content-Type: text/plain; charset=utf-8
was returned on all requests. #5183-proxy.compare-skip-recent-samples
to avoid racing with recording rule evaluation. #5561-backend.skip-tls-verify
to optionally skip TLS verification on backends. #5656get-started
documentation directory. #5476MimirRulerTooManyFailedQueries
runbook. #5586MimirRequestErrors
runbook for alertmanager. #5694-source-service
and -destination-service
flags are now required and the -service
flag has been removed. #5486-help
flag is passed. #5412All changes in this release: https://github.com/grafana/mimir/compare/mimir-2.9.0...mimir-2.10.0
This release contains 2 PRs from 1 authors. Thank you!
All changes in this release: https://github.com/grafana/mimir/compare/mimir-2.9.0...mimir-2.9.1
This release contains 5 PRs from 3 authors. Thank you!
not found
errors on label values API during head compaction. #5957All changes in this release: https://github.com/grafana/mimir/compare/mimir-2.10.0-rc.1...mimir-2.10.0-rc.2
This release contains 12 PRs from 4 authors. Thank you!
-ruler-storage.cache.*
)-ingester.ring.excluded-zones
)-query-frontend.query-sharding-target-series-per-shard
)-query-frontend.results-cache-ttl-for-cardinality-query
)-query-frontend.results-cache-ttl-for-labels-query
)-query-frontend.max-query-expression-size-bytes
)-overrides-exporter.ring.enabled
)-overrides-exporter.enabled-metrics
)-query-frontend.results-cache-ttl
, -query-frontend.results-cache-ttl-for-out-of-order-time-window
)-tenant-federation.max-concurrent
to adjust the max number of per-tenant queries that can be run at a time when executing a single multi-tenant query. #5874mimirtool analyse grafana
. This allows the tool to work correctly when running against Grafana instances with more than a 1000 dashboards. #5825__name__
matcher. #5911label_values(<label_name>)
when running mimirtool analyse grafana
. #5832All changes in this release: https://github.com/grafana/mimir/compare/mimir-2.10.0-rc.0...mimir-2.10.0-rc.1
This release contains 434 PRs from 54 authors, including new contributors Aaron Sanders, Alexander Proschek, Aljoscha Pörtner, balazs92117, Francois Gouteroux, Franco Posa, Heather Yuan, jingyang, kendrickclark, m4r1u2, Milan Plžík, Samir Teymurov, Sven Haardiek, Thomas Schaaf, Tiago Posse. Thank you!
Pending, draft version can be seen at: https://github.com/grafana/mimir/pull/5873
blocks_storage.bucket_store.index_header.verify_on_load: true
. #5174-querier.streaming-chunks-per-ingester-buffer-size
flag to 256. #5203ACTIVE
state in the ring. #5342-querier.prefer-streaming-chunks
to -querier.prefer-streaming-chunks-from-ingesters
to enable streaming chunks from ingesters to queriers. #5182-query-frontend.cache-unaligned-requests
has been moved from a global flag to a per-tenant override. #5312cortex_ingester_shipper_dir_syncs_total
and cortex_ingester_shipper_dir_sync_failures_total
metrics. The former metric was not much useful, and the latter was never incremented. #5396-shutdown-delay
flag is no longer experimental. #5701-validation.create-grace-period
is now enforced in the ingester too, other than distributor and query-frontend. If you've configured -validation.create-grace-period
then make sure the configuration is applied to ingesters too. #5712-validation.create-grace-period
is now enforced for examplars too in the distributor. If an examplar has timestamp greater than "now + grace_period", then the exemplar will be dropped and the metric cortex_discarded_exemplars_total{reason="exemplar_too_far_in_future",user="..."}
increased. #5761-validation.create-grace-period
is now enforced in the query-frontend even when the configured value is 0. When the value is 0, the query end time range is truncated to the current real-world time. #5829blocks-storage.bucket-store
and use a new configurations in blocks-storage.bucket-store.index-header
, deprecated configuration will be removed in Mimir 2.12. Configuration changes: #5726
-blocks-storage.bucket-store.index-header-lazy-loading-enabled
is deprecated, use the new configuration -blocks-storage.bucket-store.index-header.lazy-loading-enabled
-blocks-storage.bucket-store.index-header-lazy-loading-idle-timeout
is deprecated, use the new configuration -blocks-storage.bucket-store.index-header.lazy-loading-idle-timeout
-blocks-storage.bucket-store.index-header-lazy-loading-concurrency
is deprecated, use the new configuration -blocks-storage.bucket-store.index-header.lazy-loading-concurrency
-blocks-storage.bucket-store.chunks-cache.fine-grained-chunks-caching-enabled
, -blocks-storage.bucket-store.fine-grained-chunks-caching-ranges-per-series
. #5816blocks-storage.tsdb.max-tsdb-opening-concurrency-on-startup
. #5850distributor.service_overload_status_code_on_rate_limit_enabled
flag for configuring status code to 529 instead of 429 upon rate limit exhaustion. #5752count_method
parameter which enables counting active series #5136-query-frontend.cache-results
is enabled, and -query-frontend.results-cache-ttl-for-cardinality-query
or -query-frontend.results-cache-ttl-for-labels-query
set to a value greater than 0. The following metrics have been added to track the query results cache hit ratio per request_type
: #5212 #5235 #5426 #5524
cortex_frontend_query_result_cache_requests_total{request_type="query_range|cardinality|label_names_and_values"}
cortex_frontend_query_result_cache_hits_total{request_type="query_range|cardinality|label_names_and_values"}
-<prefix>.s3.list-objects-version
flag to configure the S3 list objects version. #5099-ingester.read-path-cpu-utilization-limit
-ingester.read-path-memory-utilization-limit
-ingester.log-utilization-based-limiter-cpu-samples
file
, rule_group
and rule_name
. #5291-ingester.ring.token-generation-strategy: spread-minimizing
and -ingester.ring.spread-minimizing-zones: <all available zones>
. In that case -ingester.ring.tokens-file-path
must be empty. #5308 #5324-ingester.ring.spread-minimizing-join-ring-in-order
that allows an ingester to register tokens in the ring only after all previous ingesters (with ID lower than its own ID) have already been registered. #5541-blocks-storage.tsdb.early-head-compaction-min-in-memory-series
, and the ingester estimates that the per-tenant TSDB Head compaction will reduce in-memory series by at least -blocks-storage.tsdb.early-head-compaction-min-estimated-series-reduction-percentage
. #5371cortex_ingester_active_native_histogram_series
, cortex_ingester_active_native_histogram_series_custom_tracker
, cortex_ingester_active_native_histogram_buckets
, cortex_ingester_active_native_histogram_buckets_custom_tracker
. The first 2 are the subsets of the existing and unmodified cortex_ingester_active_series
and cortex_ingester_active_series_custom_tracker
respectively, only tracking native histogram series, and the last 2 are the equivalents for tracking the number of buckets in native histogram series. #5318-<prefix>.s3.native-aws-auth-enabled
that allows to enable the default credentials provider chain of the AWS SDK. #5636-ingester.client.circuit-breaker.enabled
, -ingester.client.circuit-breaker.failure-threshold
, or -ingester.client.circuit-breaker.cooldown-period
or their corresponding YAML. #5650max_global_metadata_per_user
, max_global_metadata_per_metric
, request_rate
, request_burst_size
, alertmanager_notification_rate_limit
, alertmanager_max_dispatcher_aggregation_groups
, alertmanager_max_alerts_count
, alertmanager_max_alerts_size_bytes
) and added flag -overrides-exporter.enabled-metrics
to explicitly configure desired metrics, e.g. -overrides-exporter.enabled-metrics=request_rate,ingestion_rate
. Default value for this flag is: ingestion_rate,ingestion_burst_size,max_global_series_per_user,max_global_series_per_metric,max_global_exemplars_per_user,max_fetched_chunks_per_query,max_fetched_series_per_query,ruler_max_rules_per_rule_group,ruler_max_rule_groups_per_tenant
. #5376-timeseries-unmarshal-caching-optimization-enabled=false
. #5137-<prefix>.connect-timeout
-<prefix>.connect-backoff-base-delay
-<prefix>.connect-backoff-max-delay
-<prefix>.initial-stream-window-size
-<prefix>.initial-connection-window-size
-distributor.write-requests-buffer-pooling-enabled
to true
. #5195 #5805 #5830-querier.minimize-ingester-requests
option to initially query only the minimum set of ingesters required to reach quorum. #5202 #5259 #5263cortex_ruler_sync_rules_duration_seconds
metric, tracking the time spent syncing all rule groups owned by the ruler instance. #5311blocks-storage.bucket-store.index-header-lazy-loading-concurrency
config option to limit the number of concurrent index-headers loads when lazy loading. #5313 #5605cortex_querier_queries_rejected_total
metric that counts the number of queries rejected due to hitting a limit (eg. max series per query or max chunks per query). #5316 #5440 #5450-querier.minimize-ingester-requests-hedging-delay
option to initiate requests to further ingesters when request minimisation is enabled and not all initial requests have completed. #5368-ingester.client.*
flags to make it clear that these are used by both queriers and distributors. #5375-querier.prefer-streaming-chunks-from-store-gateways=true
. #5182max-chunks-per-query
limit earlier in query processing when streaming chunks from ingesters to queriers to avoid unnecessarily consuming resources for queries that will be aborted. #5369 #5447cortex_ingester_shipper_last_successful_upload_timestamp_seconds
metric tracking the last successful TSDB block uploaded to the bucket (unix timestamp in seconds). #5396cortex_ingester_utilization_limiter_current_cpu_load
: The current exponential weighted moving average of the ingester's CPU loadcortex_ingester_utilization_limiter_current_memory_usage_bytes
: The current ingester memory utilizationinsight=true
field to ruler's prometheus component for rule evaluation logs. #5510cortex_distributor_instance_rejected_requests_total
and cortex_ingester_instance_rejected_requests_total
respectively. #5551-log.buffered
: Enable buffered logging-compactor.no-blocks-file-cleanup-enabled
option. #5648-store-gateway.sharding-ring.auto-forget-enabled
configuration parameter to control whether store-gateway auto-forget feature should be enabled or disabled (enabled by default). #5702cortex_block_upload_api_blocks_total
, cortex_block_upload_api_bytes_total
, and cortex_block_upload_api_files_total
. #5738-log.rate-limit-enabled
-log.rate-limit-logs-per-second
-log.rate-limit-logs-per-second-burst
cortex_ingester_tsdb_head_min_timestamp_seconds
and cortex_ingester_tsdb_head_max_timestamp_seconds
metrics which return min and max time of all TSDB Heads open in an ingester. #5786 #5815-querier.max-estimated-fetched-chunks-per-query-multiplier
. #5765__name__
posting group in selection in order to reduce the number of object storage API calls. #5246timestamp()
function fail with execution: attempted to read series at index 0 from stream, but the stream has already been exhausted
if streaming chunks from ingesters to queriers is enabled. #5370memberlist_client_kv_store_count
metric that used to exist in Cortex, but got lost during dskit updates before Mimir 2.0. #5377cortex_ingester_client_request_duration_seconds
metric did not include streaming query requests that did not return any series. #5695MimirProvisioningTooManyActiveSeries
alert. You should configure -ingester.instance-limits.max-series
and rely on MimirIngesterReachingSeriesLimit
alert instead. #5593MimirProvisioningTooManyWrites
alert. The alerting threshold used in this alert was chosen arbitrarily and ingesters receiving an higher number of samples / sec don't necessarily have any issue. You should rely on SLOs metrics and alerts instead. #5706MimirRequestErrors
or MimirRequestLatency
alert for the /debug/pprof
endpoint. #5826MimirIngestedDataTooFarInTheFuture
warning alert that triggers when Mimir ingests sample with timestamp more than 1h in the future. #5822MimirIngesterRestarts
to fire only when the ingester container is restarted, excluding the cases the pod is rescheduled. #5397MimirIngesterHasNotShippedBlocks
and MimirIngesterHasNotShippedBlocksSinceStart
alerts. #5396MimirGossipMembersMismatch
to include admin-api
and custom compactor pods. admin-api
is a GEM component. #5641 #5797_config.querier.concurrency
configuration option and replaced it with _config.querier_max_concurrency
and _config.ruler_querier_max_concurrency
to allow to easily fine tune it for different querier deployments. #5322_config.multi_zone_ingester_max_unavailable
to 50. #5327maxSurge
and maxUnavailable
are set to 15%
and 0
. #5714autoscaling_alertmanager_enabled: true
. #5194 #5249track_sizes
feature for Memcached pods to help determine cache efficiency. #5209PodDisruptionBudget
s for compactor, continuous-test, distributor, overrides-exporter, querier, query-frontend, query-scheduler, rollout-operator, ruler, ruler-querier, ruler-query-frontend, ruler-query-scheduler, and all memcached workloads. #5098_config.shuffle_sharding.target_series_per_ingester
and _config.shuffle_sharding.target_utilization_percentage
values. #5470_config.autoscaling_distributor_cpu_target_utilization
. #5525_config.ruler_remote_evaluation_max_query_response_size_bytes
to easily set the maximum query response size allowed (in bytes). #5592GOMAXPROCS
based on the CPU request. This should reduce distributor CPU utilization, assuming the CPU request is set to a value close to the actual utilization. #5588GOMAXPROCS
based on the CPU request. This should reduce noisy neighbour issues created by the querier, whose CPU utilization could eventually saturate the Kubernetes node if unbounded. #5646 #5658null
in the *_env_map
objects (e.g. store_gateway_env_map+:: { 'field': null}
). #5599etcd
. #5589autoscaling_querier_target_utilization
(defaults to 0.75
)autoscaling_mimir_read_target_utilization
(defaults to 0.75
)autoscaling_ruler_querier_cpu_target_utilization
(defaults to 1
)autoscaling_distributor_memory_target_utilization
(defaults to 1
)autoscaling_ruler_cpu_target_utilization
(defaults to 1
)autoscaling_query_frontend_cpu_target_utilization
(defaults to 1
)autoscaling_ruler_query_frontend_cpu_target_utilization
(defaults to 1
)autoscaling_alertmanager_cpu_target_utilization
(defaults to 1
)v0.7.0
. #5718Content-Type
response header from backend. Previously Content-Type: text/plain; charset=utf-8
was returned on all requests. #5183-proxy.compare-skip-recent-samples
to avoid racing with recording rule evaluation. #5561-backend.skip-tls-verify
to optionally skip TLS verification on backends. #5656get-started
documentation directory. #5476MimirRulerTooManyFailedQueries
runbook. #5586MimirRequestErrors
runbook for alertmanager. #5694-source-service
and -destination-service
flags are now required and the -service
flag has been removed. #5486-help
flag is passed. #5412All changes in this release: https://github.com/grafana/mimir/compare/mimir-2.9.0...mimir-2.10.0-rc.0
This release contains 252 PRs from 46 authors, including new contributors Alex R, Alexander Soelberg Heidarsson, Alexander Weaver, Benjamin Lazarecki, Dhanu Saputra, Dominik Süß, Fiona Liao, Jonathan Halterman, Kristian Bremberg, MattiasSegerdahl, Salva Corts, Stephanie Closson, willychrisza. Thank you!
Grafana Labs is excited to announce version 2.9 of Grafana Mimir.
The highlights that follow include the top features, enhancements, and bugfixes in this release. For the complete list of changes, see the changelog.
datacenter="dc1"
), Mimir 2.9 will fetch a reduced volume of index data, which leads to a significant reduction in memory allocations in the store-gateway.-ruler-storage.cache.*
CLI flags or their respective YAML config options.-ruler.poll-interval
, which has then been relaxed from every 1m
to every 10m
. The new behaviour is enabled globally by default but can be disabled with -ruler.sync-rules-on-changes-enabled=false
or tuned at a per-tenant level.The Grafana Mimir and Grafana Enterprise Metrics Helm chart is now released independently. See the Grafana Mimir Helm chart documentation.
In Grafana Mimir 2.9 we have removed the following previously deprecated or experimental metrics:
cortex_bucket_store_chunk_pool_requested_bytes_total
cortex_bucket_store_chunk_pool_returned_bytes_total
The following configuration options are deprecated and will be removed in Grafana Mimir 2.11:
-querier.query-ingesters-within
. This configuration is moved to per-tenant overrides.-blocks-storage.bucket-store.bucket-index.enabled
.-blocks-storage.bucket-store.chunk-pool-min-bucket-size-bytes
, -blocks-storage.bucket-store.chunk-pool-max-bucket-size-bytes
and -blocks-storage.bucket-store.max-chunk-pool-bytes
.-querier.iterators
and -query.batch-iterators
.The following configuration options that were deprecated in 2.7 are removed:
-blocks-storage.bucket-store.chunks-cache.subrange-size
. A fixed value of 16000 is now always used.-blocks-storage.bucket-store.consistency-delay
.-compactor.consistency-delay
.-ingester.ring.readiness-check-ring-health
.The following experimental options and features are now stable:
-query-frontend.query-sharding-max-regexp-size-bytes
.-query-scheduler.max-used-instances
.-(alertmanager|blocks|ruler)-storage.storage-prefix
.-compactor.first-level-compaction-wait-period
.-usage-stats.enabled
and -usage-stats.installation-mode
.-query-frontend.query-sharding-target-series-per-shard
.The following configuration option defaults were changed:
-query-frontend.query-sharding-max-regexp-size-bytes
was changed from 0
to 4096
. As a result, queries with regex matchers exceeding this limit will not be sharded by default.-compactor.partial-block-deletion-delay
was changed from 0s
to 1d
. As a result, partial blocks resulting from a failed block upload or deletion will be cleaned up automatically.-ruler.poll-interval
was changed from 1m
to 10m
.-query-frontend.query-sharding-max-regexp-size-bytes
from 0
to 4096
. #4932-querier.query-ingesters-within
has been moved from a global flag to a per-tenant override. #4287-blocks-storage.tsdb.retention-period
instead of -querier.query-ingesters-within
for calculating the lookback period for shuffle sharded ingesters. Setting -querier.query-ingesters-within=0
no longer disables shuffle sharding on the read path. #4287/api/v1/upload/block/{block}/files
endpoint now allows file uploads with no Content-Length
. #4956-blocks-storage.bucket-store.max-chunk-pool-bytes
-blocks-storage.bucket-store.chunk-pool-min-bucket-size-bytes
-blocks-storage.bucket-store.chunk-pool-max-bucket-size-bytes
cortex_bucket_store_chunk_pool_requested_bytes_total
and cortex_bucket_store_chunk_pool_returned_bytes_total
. #4996-compactor.partial-block-deletion-delay
to 1d
. This will automatically clean up partial blocks that were a result of failed block upload or deletion. #5026-compactor.consistency-delay
has been removed. #5050-blocks-storage.bucket-store.consistency-delay
has been removed. #5050-blocks-storage.bucket-store.bucket-index.enabled
has been deprecated and will be removed in Mimir 2.11. Mimir is running by default with the bucket index enabled since version 2.0, and starting from the version 2.11 it will not be possible to disable it. #5051-querier.iterators
and -query.batch-iterators
have been deprecated and will be removed in Mimir 2.11. Mimir runs by default with -querier.batch-iterators=true
, and starting from version 2.11 it will not be possible to change this. #5114-compactor.first-level-compaction-wait-period
to 25m. #5128-ruler.poll-interval
from 1m
to 10m
. Starting from this release, the configured rule groups will also be re-synced each time they're modified calling the ruler configuration API. #5170-query-frontend.log-query-request-headers
to enable logging of request headers in query logs. #5030-validation.max-native-histogram-buckets
to be able to ignore native histogram samples that have too many buckets. #4765stage
label to the metric cortex_bucket_store_series_data_touched
. This label now applies to data_type="chunks"
and data_type="series"
. The stage
label has 2 values: processed
- the number of series that parsed - and returned
- the number of series selected from the processed bytes to satisfy the query. #4797 #4830__meta_tenant_id
label available in relabeling rules configured via metric_relabel_configs
. #4725compactor.block-upload-max-block-size-bytes
or compactor_block_upload_max_block_size_bytes
to limit the byte size of uploaded or validated blocks. #4680queryFromGeneratorURL
returning query URL decoded query from the GeneratorURL
field of an alert. #4301-ruler-storage.cache.*
CLI flags or their respective YAML config options. #4950 #5054/store-gateway/prepare-shutdown
endpoint for gracefully scaling down of store-gateways. A gauge cortex_store_gateway_prepare_shutdown_requested
has been introduced for tracing this process. #4955-server.log-request-headers
enables logging HTTP request headers, -server.log-request-headers-exclude-list
lists headers which should not be logged. #4922/api/v1/upload/block/{block}/files
endpoint now disables read and write HTTP timeout, overriding -server.http-read-timeout
and -server.http-write-timeout
values. This is done to allow large file uploads to succeed. #4956cortex_alertmanager_notifications_failed_total
(added reason
label)cortex_alertmanager_nflog_maintenance_total
cortex_alertmanager_nflog_maintenance_errors_total
cortex_alertmanager_silences_maintenance_total
cortex_alertmanager_silences_maintenance_errors_total
cortex_request_duration_seconds
metric family. #4987<prometheus-http-prefix>/api/v1/format_query
to format a PromQL query. #4373cortex_query_frontend_regexp_matcher_count
and cortex_query_frontend_regexp_matcher_optimized_count
metrics to track optimization of regular expression label matchers. #4813-enable-go-runtime-metrics
flag to expose all go runtime metrics as Prometheus metrics. #5009-ruler.poll-interval
. The new behavior is enabled by default, but can be disabled with -ruler.sync-rules-on-changes-enabled=false
(configurable on a per-tenant basis too). If you disable the new behaviour, then you may want to revert -ruler.poll-interval
to 1m
. #4975 #5053 #5115 #5170cortex_bucket_store_series_request_stage_duration_seconds{stage="load_index_header"}
. Now index header loading will be visible in the "Mimir / Queries" dashboard in the "Series request p99/average latency" panels. #5011 #5062-querier.prefer-streaming-chunks=true
. #4886 #5078 #5094 #5126alpine:3.17.3
to alpine:3.18.0
. #5065meta.json
files. #5063-distributor.request-rate-limit
and -distributor.request-burst-size
) and their associated YAML configuration are now stable. #5124type=alert|record
query parameter for the API endpoint <prometheus-http-prefix>/api/v1/rules
. #4302MimirIngesterReachingTenantsLimit
runbook. #4744 #4752symbol table size exceeds
case to MimirCompactorHasNotSuccessfullyRunCompaction
runbook. #4945MimirQuerierHighRefetchRate
. #4980MimirTenantHasPartialBlocks
. This is obsoleted by the changed default of -compactor.partial-block-deletion-delay
to 1d
, which will auto remediate this alert. #5026MimirIngesterTSDBWALCorrupted
now only fires when there are more than one corrupted WALs in single-zone deployments and when there are more than two zones affected in multi-zone deployments. #4920MimirRolloutStuck
and MimirCompactorHasNotUploadedBlocks
rules in order to distinguish them. #5023MimirAllocatingTooMuchMemory
alert for any matching container outside of namespaces where Mimir is running. #5089alertmanager_args
to mimir-backend
when running in read-write deployment mode. Remove hardcoded filesystem
alertmanager storage. This moves alertmanager's data-dir to /data/alertmanager
by default. #4907 #4921-pdb
suffix from PodDisruptionBudget
names. This will create new PodDisruptionBudget
resources. Make sure to prune the old resources; otherwise, rollouts will be blocked. #5109-query-frontend.query-sharding-target-series-per-shard
by default if the results cache is enabled. #5128-blocks-storage.tsdb.head-compaction-interval=15m
to spread TSDB head compaction over a wider time range. #4870-blocks-storage.tsdb.wal-replay-concurrency
to CPU request minus 1. #4864-compactor.first-level-compaction-wait-period
to TSDB head compaction interval plus 10 minutes. #4872GOMEMLIMIT
to the memory request value. This should reduce the likelihood the store-gateway may go out of memory, at the cost of an higher CPU utilization due to more frequent garbage collections when the memory utilization gets closer or above the configured requested memory. #4971GOMAXPROCS
based on the CPU request. This should reduce the likelihood a high load on the store-gateway will slow down the entire Kubernetes node. #5104store_gateway_lazy_loading_enabled
configuration option which combines disabled lazy-loading and reducing blocks sync concurrency. Reducing blocks sync concurrency improves startup times with disabled lazy loading on HDDs. #5025rollout-operator
image to v0.6.0
. #5155-ruler.alertmanager-url
to mimir-backend
when running in read-write deployment mode. #4892--strict
is provided. #5035--namespaces-regex
and --ignore-namespaces-regex
. #5100-prometheus-http-prefix
. #4966--folder-title
to limit dashboards analysis based on their exact folder title. #4973--service
flag is now required to be specified (accepted values are gcs
or abs
). #4756All changes in this release: https://github.com/grafana/mimir/compare/mimir-2.8.0...mimir-2.9.0
This release contains 260 PRs from 46 authors. Thank you!
Grafana Labs is excited to announce version 2.9 of Grafana Mimir.
The highlights that follow include the top features, enhancements, and bugfixes in this release. For the complete list of changes, see the changelog.
datacenter="dc1"
), Mimir 2.9 will fetch a reduced volume of index data, which leads to a significant reduction in memory allocations in the store-gateway.-ruler-storage.cache.*
CLI flags or their respective YAML config options.-ruler.sync-rules-on-changes-enabled=false
or tuned at a per-tenant level.The Grafana Mimir and Grafana Enterprise Metrics Helm chart is now released independently. See the Grafana Mimir Helm chart documentation.
In Grafana Mimir 2.9 we have removed the following previously deprecated or experimental metrics:
cortex_bucket_store_chunk_pool_requested_bytes_total
cortex_bucket_store_chunk_pool_returned_bytes_total
The following configuration options are deprecated and will be removed in Grafana Mimir 2.11:
-querier.query-ingesters-within
. This configuration is moved to per-tenant overrides.-blocks-storage.bucket-store.bucket-index.enabled
.-blocks-storage.bucket-store.chunk-pool-min-bucket-size-bytes
, -blocks-storage.bucket-store.chunk-pool-max-bucket-size-bytes
and -blocks-storage.bucket-store.max-chunk-pool-bytes
.querier.iterators
and -query.batch-iterators
.The following configuration options that were deprecated in 2.7 are removed:
-blocks-storage.bucket-store.chunks-cache.subrange-size
. A fixed value of 16000 is now always used.-blocks-storage.bucket-store.consistency-delay
.-compactor.consistency-delay
.-ingester.ring.readiness-check-ring-health
.The following experimental options and features are now stable:
-query-frontend.query-sharding-max-regexp-size-bytes
.-query-scheduler.max-used-instances
.-(alertmanager|blocks|ruler)-storage.storage-prefix
.-compactor.first-level-compaction-wait-period
.-usage-stats.enabled
and -usage-stats.installation-mode
.-query-frontend.query-sharding-target-series-per-shard
.The following configuration option defaults were changed:
-query-frontend.query-sharding-max-regexp-size-bytes
was changed from 0
to 4096
. As a result, queries with regex matchers exceeding this limit will not be sharded by default.-compactor.partial-block-deletion-delay
was changed from 0s
to 1d
. As a result, partial blocks resulting from a failed block upload or deletion will be cleaned up automatically.-ruler.poll-interval
was changed from 1m
to 10m
.-query-frontend.query-sharding-max-regexp-size-bytes
from 0
to 4096
. #4932-querier.query-ingesters-within
has been moved from a global flag to a per-tenant override. #4287-blocks-storage.tsdb.retention-period
instead of -querier.query-ingesters-within
for calculating the lookback period for shuffle sharded ingesters. Setting -querier.query-ingesters-within=0
no longer disables shuffle sharding on the read path. #4287/api/v1/upload/block/{block}/files
endpoint now allows file uploads with no Content-Length
. #4956-blocks-storage.bucket-store.max-chunk-pool-bytes
-blocks-storage.bucket-store.chunk-pool-min-bucket-size-bytes
-blocks-storage.bucket-store.chunk-pool-max-bucket-size-bytes
cortex_bucket_store_chunk_pool_requested_bytes_total
and cortex_bucket_store_chunk_pool_returned_bytes_total
. #4996-compactor.partial-block-deletion-delay
to 1d
. This will automatically clean up partial blocks that were a result of failed block upload or deletion. #5026-compactor.consistency-delay
has been removed. #5050-blocks-storage.bucket-store.consistency-delay
has been removed. #5050-blocks-storage.bucket-store.bucket-index.enabled
has been deprecated and will be removed in Mimir 2.11. Mimir is running by default with the bucket index enabled since version 2.0, and starting from the version 2.11 it will not be possible to disable it. #5051-querier.iterators
and -query.batch-iterators
have been deprecated and will be removed in Mimir 2.11. Mimir runs by default with -querier.batch-iterators=true
, and starting from version 2.11 it will not be possible to change this. #5114-compactor.first-level-compaction-wait-period
to 25m. #5128-ruler.poll-interval
from 1m
to 10m
. Starting from this release, the configured rule groups will also be re-synced each time they're modified calling the ruler configuration API. #5170-query-frontend.log-query-request-headers
to enable logging of request headers in query logs. #5030-validation.max-native-histogram-buckets
to be able to ignore native histogram samples that have too many buckets. #4765stage
label to the metric cortex_bucket_store_series_data_touched
. This label now applies to data_type="chunks"
and data_type="series"
. The stage
label has 2 values: processed
- the number of series that parsed - and returned
- the number of series selected from the processed bytes to satisfy the query. #4797 #4830__meta_tenant_id
label available in relabeling rules configured via metric_relabel_configs
. #4725compactor.block-upload-max-block-size-bytes
or compactor_block_upload_max_block_size_bytes
to limit the byte size of uploaded or validated blocks. #4680queryFromGeneratorURL
returning query URL decoded query from the GeneratorURL
field of an alert. #4301-ruler-storage.cache.*
CLI flags or their respective YAML config options. #4950 #5054/store-gateway/prepare-shutdown
endpoint for gracefully scaling down of store-gateways. A gauge cortex_store_gateway_prepare_shutdown_requested
has been introduced for tracing this process. #4955-server.log-request-headers
enables logging HTTP request headers, -server.log-request-headers-exclude-list
lists headers which should not be logged. #4922/api/v1/upload/block/{block}/files
endpoint now disables read and write HTTP timeout, overriding -server.http-read-timeout
and -server.http-write-timeout
values. This is done to allow large file uploads to succeed. #4956cortex_alertmanager_notifications_failed_total
(added reason
label)cortex_alertmanager_nflog_maintenance_total
cortex_alertmanager_nflog_maintenance_errors_total
cortex_alertmanager_silences_maintenance_total
cortex_alertmanager_silences_maintenance_errors_total
cortex_request_duration_seconds
metric family. #4987<prometheus-http-prefix>/api/v1/format_query
to format a PromQL query. #4373cortex_query_frontend_regexp_matcher_count
and cortex_query_frontend_regexp_matcher_optimized_count
metrics to track optimization of regular expression label matchers. #4813-enable-go-runtime-metrics
flag to expose all go runtime metrics as Prometheus metrics. #5009-ruler.poll-interval
. The new behavior is enabled by default, but can be disabled with -ruler.sync-rules-on-changes-enabled=false
(configurable on a per-tenant basis too). If you disable the new behaviour, then you may want to revert -ruler.poll-interval
to 1m
. #4975 #5053 #5115 #5170cortex_bucket_store_series_request_stage_duration_seconds{stage="load_index_header"}
. Now index header loading will be visible in the "Mimir / Queries" dashboard in the "Series request p99/average latency" panels. #5011 #5062-querier.prefer-streaming-chunks=true
. #4886 #5078 #5094 #5126alpine:3.17.3
to alpine:3.18.0
. #5065meta.json
files. #5063-distributor.request-rate-limit
and -distributor.request-burst-size
) and their associated YAML configuration are now stable. #5124type=alert|record
query parameter for the API endpoint <prometheus-http-prefix>/api/v1/rules
. #4302MimirIngesterReachingTenantsLimit
runbook. #4744 #4752symbol table size exceeds
case to MimirCompactorHasNotSuccessfullyRunCompaction
runbook. #4945MimirQuerierHighRefetchRate
. #4980MimirTenantHasPartialBlocks
. This is obsoleted by the changed default of -compactor.partial-block-deletion-delay
to 1d
, which will auto remediate this alert. #5026MimirIngesterTSDBWALCorrupted
now only fires when there are more than one corrupted WALs in single-zone deployments and when there are more than two zones affected in multi-zone deployments. #4920MimirRolloutStuck
and MimirCompactorHasNotUploadedBlocks
rules in order to distinguish them. #5023MimirAllocatingTooMuchMemory
alert for any matching container outside of namespaces where Mimir is running. #5089alertmanager_args
to mimir-backend
when running in read-write deployment mode. Remove hardcoded filesystem
alertmanager storage. This moves alertmanager's data-dir to /data/alertmanager
by default. #4907 #4921-pdb
suffix from PodDisruptionBudget
names. This will create new PodDisruptionBudget
resources. Make sure to prune the old resources; otherwise, rollouts will be blocked. #5109-query-frontend.query-sharding-target-series-per-shard
by default if the results cache is enabled. #5128-blocks-storage.tsdb.head-compaction-interval=15m
to spread TSDB head compaction over a wider time range. #4870-blocks-storage.tsdb.wal-replay-concurrency
to CPU request minus 1. #4864-compactor.first-level-compaction-wait-period
to TSDB head compaction interval plus 10 minutes. #4872GOMEMLIMIT
to the memory request value. This should reduce the likelihood the store-gateway may go out of memory, at the cost of an higher CPU utilization due to more frequent garbage collections when the memory utilization gets closer or above the configured requested memory. #4971GOMAXPROCS
based on the CPU request. This should reduce the likelihood a high load on the store-gateway will slow down the entire Kubernetes node. #5104store_gateway_lazy_loading_enabled
configuration option which combines disabled lazy-loading and reducing blocks sync concurrency. Reducing blocks sync concurrency improves startup times with disabled lazy loading on HDDs. #5025rollout-operator
image to v0.6.0
. #5155-ruler.alertmanager-url
to mimir-backend
when running in read-write deployment mode. #4892--strict
is provided. #5035--namespaces-regex
and --ignore-namespaces-regex
. #5100-prometheus-http-prefix
. #4966--folder-title
to limit dashboards analysis based on their exact folder title. #4973--service
flag is now required to be specified (accepted values are gcs
or abs
). #4756Full Changelog: https://github.com/grafana/mimir/compare/mimir-2.8.0...mimir-2.9.0-rc.1