You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: