Skip to content
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

Modify Default Deduplication Behavior for Alerts #3655

Open
mastercactapus opened this issue Feb 6, 2024 · 0 comments
Open

Modify Default Deduplication Behavior for Alerts #3655

mastercactapus opened this issue Feb 6, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@mastercactapus
Copy link
Member

What problem would you like to solve? Please describe:
The current default deduplication (dedup) behavior for alerts is a combination of the summary and details fields. This can limit the dedup functionality especially in instances where only summaries are sent in many messages like (SMS or voice).

Describe the solution you'd like:
It would be beneficial to modify the default dedup behavior to be based on the summary field alone. This change would not affect alerts that are sending an explicit dedup field.

Describe alternatives you've considered:
A possible alternative could be to allow customizable dedup rules, however this could add complexity. To keep it simpler and more streamlined, basing dedup on the summary field seems most reasonable.

Additional context:
The dedup hash in the database is already versioned, and can be used to ensure that existing alerts continue to use the old behavior. This means we could check both hashes before creating a new one to maintain backward compatibility.

@mastercactapus mastercactapus added the enhancement New feature or request label Feb 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant