You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add support for Max Series Per Query for block storage and streaming ingesters (#4179)
* Add support for Max Series Per Query for block storage and streaming ingesters and update limits.go to reflect changes
Signed-off-by: Tyler Reid <[email protected]>
* Fix spacing issues
Signed-off-by: Tyler Reid <[email protected]>
* Review and linter changes
Signed-off-by: Tyler Reid <[email protected]>
* Update docs
Signed-off-by: Tyler Reid <[email protected]>
Signed-off-by: Tyler Reid <[email protected]>
* Add changelog for series per query limit
Signed-off-by: Tyler Reid <[email protected]>
* Apply suggestions from code review
Co-authored-by: Marco Pracucci <[email protected]>
Signed-off-by: Tyler Reid <[email protected]>
* address review comments
Signed-off-by: Tyler Reid <[email protected]>
* Added integration test for series per query limit
Signed-off-by: Tyler Reid <[email protected]>
* Fix up integration test
Signed-off-by: Tyler Reid <[email protected]>
* Add new config option querier.max-series-per-query and use that instead of ingester.max-series-per-query for series per query limit
Signed-off-by: Tyler Reid <[email protected]>
* Update docs to show new cli flag and other review changes
Signed-off-by: Tyler Reid <[email protected]>
* Check error to resolve linter issue
Signed-off-by: Tyler Reid <[email protected]>
* Clean white noise
Signed-off-by: Marco Pracucci <[email protected]>
Co-authored-by: Tyler Reid <[email protected]>
Co-authored-by: Tyler Reid <[email protected]>
Co-authored-by: Marco Pracucci <[email protected]>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,7 @@
7
7
-`-alertmanager.receivers-firewall.block.cidr-networks` renamed to `-alertmanager.receivers-firewall-block-cidr-networks`
8
8
-`-alertmanager.receivers-firewall.block.private-addresses` renamed to `-alertmanager.receivers-firewall-block-private-addresses`
9
9
*[CHANGE] Change default value of `-server.grpc.keepalive.min-time-between-pings` to `10s` and `-server.grpc.keepalive.ping-without-stream-allowed` to `true`. #4168
10
+
*[FEATURE] Querier: Added new `-querier.max-fetched-series-per-query` flag. When Cortex is running with blocks storage, the max series per query limit is enforced in the querier and applies to unique series received from ingesters and store-gateway (long-term storage). #4179
10
11
*[FEATURE] Alertmanager: Added rate-limits to notifiers. Rate limits used by all integrations can be configured using `-alertmanager.notification-rate-limit`, while per-integration rate limits can be specified via `-alertmanager.notification-rate-limit-per-integration` parameter. Both shared and per-integration limits can be overwritten using overrides mechanism. These limits are applied on individual (per-tenant) alertmanagers. Rate-limited notifications are failed notifications. It is possible to monitor rate-limited notifications via new `cortex_alertmanager_notification_rate_limited_total` metric. #4135#4163
11
12
*[ENHANCEMENT] Alertmanager: introduced new metrics to monitor operation when using `-alertmanager.sharding-enabled`: #4149
Copy file name to clipboardExpand all lines: docs/configuration/arguments.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -483,15 +483,18 @@ Valid per-tenant limits are (with their corresponding flags for default values):
483
483
Requires `-distributor.replication-factor`, `-distributor.shard-by-all-labels`, `-distributor.sharding-strategy` and `-distributor.zone-awareness-enabled` set for the ingesters too.
Enforced by the ingesters; limits the number of active metadata a user (or a given metric) can have. When running with `-distributor.shard-by-all-labels=false` (the default), this limit will enforce the maximum number of metadata a metric can have 'globally', as all metadata for a single metric will be sent to the same replication set of ingesters. This is not the case when running with `-distributor.shard-by-all-labels=true`, so the actual limit will be N/RF times higher, where N is number of ingester replicas and RF is configured replication factor.
When running Cortex with blocks storage this limit is enforced in the queriers on unique series fetched from ingesters and store-gateways (long-term storage).
0 commit comments