Vincent-TP wrote

When sending notifications, we generally prioritize displaying the most critical information first—for example, an issue like a product going offline.

Additionally, most administrators differentiate devices by assigning them different names.

  @Vincent-TP 

They do have different names, but not neccesarily all unique across every site. Your "solution" is to put the site name in every device name, which defeats the point of the site name, and adds unneccessary clutter to the dashboard. I hate to yet again reference UI but they give me clear and concise notifications without issue, I get the site name with the device names in the notifications.

Vincent-TP wrote

You can also click into the notification to view all detailed information.

I wish it was that simple. I click the notification and it just opens the app, no idea which device or site triggered the notification(s).

  @L2K WOW amazing this getting no response in a few months. I personally have disabled notifications for finding them useless but I have few devices. Yet I can feel your pain when administrating a big network with many devices and not being able to spot where a problem is and having constant spam notifications with completely useless information. Definitely needs to fill the notification/messages with useful info to quickly spot out the source of the problem, either if it's a disconnection, a device malfunction, or what ever the reason that triggered the notification.