Current State:

 
Currently, the de-duplication count for an alert stops at 100 in JSM Operations. Creating this feature request for JSM Operations on same lines as it is for Opsgenie https://jira.atlassian.com/browse/OPSGENIE-175.
 
Whenever this happens, any new payload with the same Alias coming to the integration is ignored and does not get reflected in the Alert activity log as well.
This continue to happen until the alert is closed after which system generates fresh alert for the new payload received after alert closure.

This can lead to a situation where any important payload gets ignored by the system until someone closes the alert.

Proposed Future State:

Increasing the deduplication count can help in capturing larger number of alert activities in the system and prevent the chances of missing critical alert payload coming for the same alias alert.

Workaround (e.g. Third Party Plugin):

Configure the integration in a way where Alias becomes dynamic by using variables which makes each incoming payload unique.

This can prevent the situation of missing important alerts in the system.