Skip to content

Conversation

joaquinco
Copy link
Contributor

  • Add a time throttling mechanism to prevent multiple errors to trigger notifications. It works by scheduling a notification after the last error until :throttle milliseconds have passed without an error or :time_limt milliseconds have passed from the first occurrence.

@joaquinco joaquinco force-pushed the feature/time-grouping branch from 2d8eb8f to 02422c0 Compare September 19, 2024 15:59
@joaquinco joaquinco marked this pull request as ready for review September 23, 2024 13:52
Copy link
Member

@iaguirre88 iaguirre88 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great work 💪
Just left some questions


use BoomNotifier,
notification_trigger: [:exponential],
count: [:exponential],
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Even though I like this name better I'd rather not to introduce api changes in this pull request

I think before releasing v1.0.0 we should revisit the whole api and address the changes in a separate PR

notifiers: [
# ...
],
groupping: :time,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it makes sense to have :time as other notification_trigger strategy instead of adding a new option? And maybe we could use the same time limit key we use for the others

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants