Skip to content
This repository was archived by the owner on Apr 28, 2025. It is now read-only.

fix(rules): upstream recording rule switched to sum_irate #379

Merged
merged 2 commits into from
Aug 25, 2021
Merged

fix(rules): upstream recording rule switched to sum_irate #379

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
97cf90e
fix(rules): upstream recording rule switched to sum_irate
Duologic Aug 25, 2021
79c5f75
add changelog
Duologic Aug 25, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,6 +58,7 @@
* [BUGFIX] Fixed rollout progress dashboard to correctly work when a Cortex service deployment spans across multiple zones (a zone is expected to have the `zone-[a-z]` suffix). #366
* [BUGFIX] Fixed rollout progress dashboard to include query-scheduler too. #376
* [BUGFIX] Fixed `-distributor.extend-writes` setting on ruler when `unregister_ingesters_on_shutdown` is disabled. #369
* [BUGFIX] Upstream recording rule `node_namespace_pod_container:container_cpu_usage_seconds_total:sum_irate` renamed. #379

## 1.9.0 / 2021-05-18

Expand Down
2 changes: 1 addition & 1 deletion cortex-mixin/recording_rules.libsonnet
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -213,7 +213,7 @@ local utils = import 'mixin-utils/utils.libsonnet';
sum by (cluster, namespace, deployment) (
label_replace(
label_replace(
node_namespace_pod_container:container_cpu_usage_seconds_total:sum_rate,
node_namespace_pod_container:container_cpu_usage_seconds_total:sum_irate,
Copy link
Contributor Author

@Duologic Duologic Aug 25, 2021 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure if we should reflect that in the name of this recording rule too (line 211).

"deployment", "$1", "pod", "(.*)-(?:([0-9]+)|([a-z0-9]+)-([a-z0-9]+))"
),
# The question mark in "(.*?)" is used to make it non-greedy, otherwise it
Expand Down