opensearch-project / opensearch-project/alerting

Ability to configure notification when alert auto heals

Open
#87 7 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature
Dominant language
Kotlin
Stars
82
Forks
133
Avg merge
2d 11h
Merged PRs (30d)
9

Description

Issue by alfredolopezzz
Wednesday Dec 23, 2020 at 12:23 GMT
Originally opened as https://github.com/opendistro-for-elasticsearch/alerting/issues/330


Is your feature request related to a problem? Please describe.
We have to manually ACK and close ALL alerts that ODFE-alerting sends to us (we are using Opsgenie for routing alerts to on-call engineers) even if our systems manage to auto-heal correctly (ie, metrics go back to normal). This is not scalable when managing a system with lots of alerts.

Describe the solution you'd like
We would like to be able to receive notifications when a monitor "Trigger" transitions its status from "alert triggered" to "no alerts". Right now when creating a Trigger, in the "Configure actions" section, it is only possible to specify one single message which will be used to send a notification to the destination when trigger enters the alert status.

Describe alternatives you've considered
This is a showstopper for us, we are considering moving our observability platform out of ODFE.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the monitor Trigger and its Configure actions flow, then inspect how transitions from alert triggered to no alerts are handled. Done means a configurable notification can be sent when an alert auto-heals, alongside the existing notification for entering alert status.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin
Domain
observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.