More insightful reasoning why dulicate Notification was not send representation in Frontend

[Wintermute2k6]

Is your feature request related to a problem? Please describe.

At the moment in IcingaDB-Web there is just a small Point in the Event Tab of the Service History where the Notified Users are Listed which get Notified by a Statechange.
Due to duplicate notification suppression it seems that instead of a reasonable explanation there will be set a None, instead of the correct user which should be notified. Also a addenum like This Notification wasn't send due to duplication would additionally help to get more insight why it wasn't send.

Describe the solution you'd like

It would be great if the User/Group would still be represented which should be notified and a reason why this Message was suppressed. Instead of just setting it to "None"

Describe alternatives you've considered

Maybe this will be already Solved with the new notification handling in the Future but a (probably backport might make sense) for a higher information level in the UX.

Additional context

Sorry for the German Screenshot Information.

[Wintermute2k6]

ref/NC/813228