baselime / cli Goto Github PK

Is there an existing issue for this?

• I have searched existing issues, it hasn't been reported yet

Use case description

Given I receive an alert from a COUNT query,
I would like to see the event(s) that triggered the alert,
So that I can quickly triage an issue without navigating away from my channel

Obviously a query may find many events so attaching all of them to the alert may not be feasible...

Proposed solution (optional)

Perhaps an alert can surface a single field from each event found by its query?

Is there an existing issue for this?

• I have searched existing issues, it hasn't been reported yet

Use case description

I want to create an alert that runs its query at a certain time of day. Currently, I need to wait until that time then set the frequency parameter to '1440' (i.e. minutes in a day) so that it runs once a day, at the time I created the alert.

This is inflexible and doesn't allow for more finely-tuned timings (e.g weekdays only, or less-
regular timing)

Proposed solution (optional)

Supporting the cron schedule syntax would be more convenient for the above use cases and allow a user to be more specific

Is there an existing issue for this?

• I have searched existing issues, it hasn't been reported yet

Use case description

When a function is producing constant errors, a Baselime alert with a higher frequency will "spam" the target channels with alerts for the same root issue.

It would be great to have a way of ensuring an alert that is triggered for the same root cause does not spam channels but instead has a status to say that the issue is persisting. When the errors stop, the status can revert to OK or equivalent.

It is also important for the "same root cause" check to have a way of differentiating between event (bodies) that are different but have the same underlying cause.

Proposed solution (optional)

No response