ArcGIS Monitor- List of ID/Codes for Components/Notifications?

Question

Hello Monitor Team,

Is there a way to find a list of all these IDs/codes so we know what server/component is alerting?

Thanks,

Amanda Huber

LHo · Answer

I'd like to see this feature as well. The email and webhook notifications aren't helpful as they are. One workaround would be to build several custom notifications that filter only on a specific component or metric and name them accordingly, which would get passed to the email or webhook. This would get us the component level alert, but not metric. We could build out more notifications that filter on specific metrics and name it accordingly as well. We'll end up having almost one Notification setup for each metric though..

DerekLaw · Answer

Hi @Amanda__Huber,

Thanks for sharing more details about your requirements. I will add this info into the dev backlog. And I'm sorry that Monitor 2023 is not functionally equivalent to the earlier Monitor release. We realize this and are actively working on addressing this. It's just a matter of balancing feature enhancements with dev resources.

> Also we will be at the Esri UC next week, so if you would like to talk more about this we would love to have a more enriched discussion.

Yes, absolutely. Please come by the ArcGIS Monitor kiosk, in the ArcGIS Enterprise area, in the UC Expo. Safe travels coming down and see you next week!

Amanda.Huber@threeriversparks.org_trpd · Answer

Hi @DerekLaw,

Thanks for confirming. I would be happy to share our use case.

In the new monitor version 2023.1, notification emails (and webhook payload) contain less information and less valuable information than the previous version of Monitor version 10.9.1

Notifications are crucial for alerting admins when there is a disruption in server behavior, and we rely on these heavily. When receiving notifications at the bare minimum we need to have the equivalency of information that was available at 10.9.1:

* Level of alert (warning, sever, etc)
* Server Name (title from the component)
* Name of the Error (aka Counter)
* And optionally the value compared to the threshold set
Old Monitor Notifications for reference:

Obviously the more detailed "at a glance" information in these alerts the better. Other information that we would find very valuable but has not been offered by the monitor team:

* Server Logs describing errors

It's unfortunate but we feel as though the notification/alerting component to the new Monitor is a downgrade and severely lacking equivalency. It sounds like others in the community may also be just as disappointed.

I hope this helps your team understand our use case and needs a little more. Also we will be at the Esri UC next week, so if you would like to talk more about this we would love to have a more enriched discussion.

Thanks so much as always!

- Amanda Huber