Add the "group_by" attribute for AFD alarm rules
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StackLight |
Fix Released
|
Undecided
|
Swann Croiset |
Bug Description
https:/
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
commit f86b49893e25500
Author: Swann Croiset <email address hidden>
Date: Mon Aug 22 09:14:57 2016 +0200
Add the "group_by" attribute for AFD alarm rules
The 'group_by' attribute defines an array of fields specifying on which
field(s) the received metrics should be grouped.
One alarm definition can now dynamically generate as many alarms that
there are different values for a field/dimension:
Say that the following alarm is defined:
name: 'filesystem-
severity: 'warning'
trigger:
rules:
- metric: 'fs_space_
window: 30
If the AFD filter receives metrics for 3 different 'fs' values in the
defined window:
- fs_space_
- fs_space_
- fs_space_
When evaluating the alarm, the filter will emit one AFD metric and the
Payload will contain the 2 alerts:
- fs='/' (severity=WARNING)
- fs='/var/log' (severity=WARNING)
Implements-
DocImpact
Change-Id: I4ec4fa0c462746
Changed in lma-toolchain: | |
milestone: | none → 0.10.2 |
status: | New → Confirmed |
milestone: | 0.10.2 → 1.0.0 |
Changed in lma-toolchain: | |
status: | Confirmed → Fix Committed |
Changed in lma-toolchain: | |
assignee: | nobody → Swann Croiset (swann-w) |
Changed in lma-toolchain: | |
status: | Fix Committed → Fix Released |