-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
metrics: initialize counters with 0 value
The increase() function won't recognise a move from no value -> 1 as an increase, which means it's possible for alerts to miss events. To address this, initialize every possible set of labels for each counter with a 0 value. The `semaphore_policy_sync_queue_full_failures` and `semaphore_policy_sync_requeue` CounterVecs were using the names of networksets as labels, which has an almost unbounded possible list of potential values which we obviously can't initialize ahead of time. I've decided to remove the label because: 1. It has the potential for high cardinality 2. I don't think it's necessarily important information for either metric. I'm not sure if we'd expect issues with requeueing to be networkset specific or if we'd want to split alerts by networkset. 3. If we do have an issue with a specific networkset, that information will be in the logs.
- Loading branch information
1 parent
0b2ef93
commit 82f0e8f
Showing
2 changed files
with
18 additions
and
14 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters