-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(alertmanager-dropevents-config): dropped events treatment config #439
feat(alertmanager-dropevents-config): dropped events treatment config #439
Conversation
Can you also update the README and config_example.yaml please? |
9ec3b97
to
a5ef039
Compare
Now both MR are ready ! |
Can you rebase your two PR please? |
f53bc14
to
a5cdcb4
Compare
LGTM label has been added. Git tree hash: f8a1e4db7560ccbb9bb39538417f0495e78bb117
|
… options + test Signed-off-by: Lyonel Martinez <[email protected]>
Signed-off-by: Lyonel Martinez <[email protected]>
a5cdcb4
to
da64478
Compare
@Issif It needed a second rebase, as the previous merge introduced conflict |
LGTM label has been added. Git tree hash: 77a0f2711ff5eab11881042e1533e4350ffd4208
|
A unit test failed:
|
Signed-off-by: Lyonel Martinez <[email protected]>
LGTM label has been added. Git tree hash: 6adf4f16c536c4ba1c665b1e623c284221efed6d
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Issif, Lowaiz The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind feature
Any specific area of the project related to this PR?
/area config
/area outputs
/area tests
What this PR does / why we need it:
Alertmanager output make some work on Event Drop Alerts, to re-calibrate priority and enabled Alertmanager to aggregate alerts (implemented here: #79 ). This was hard coded, and non configurable, re evaluating these alerts to Critical when the number of dropped event is
> 100
. This type of alert occurs time to time in our infra, and the re-evaluation to critical is a bit overkill.So in order to make it more configurable, I created two more config flags for Alertmanager:
DropEventThresholdList
: list ofThreshold{"value": int64, "Priority": PriorityType}
DropEventDefaultPriority
: Default Priority to override with, if no threshold has been triggeredWith the default value of thresholds, it mimic the old behavior, except for value between 1 and 10 included, where the
<10
will become>1
, in order to keep a simple config structure, avoiding the parse of an operator.I also kinda fix this behavior with the
if current prio < new prio; current prio = new prio
, as thefalcopayload.Priority
could be override with every newn_drops_*
labels.Which issue(s) this PR fixes:
None
Special notes for your reviewer:
I'll update the docs if changes are accepted