Latest Contributions by EsriEvan

Hi @SteveMcCarthy @EricJohnson-HDR, @GrahamWood-HWC  Thanks for sharing - I have been studying this and wanted to ask if you both wouldn't mind sharing a couple things: 1. Execute the following query in your Monitor Postgres and sharing the result. This will help me rule some things out. SELECT (SELECT last_value FROM metrics_id_seq) as metrics_id_seq, (SELECT last_value FROM components_id_seq) as components_id_seq, (SELECT last_value FROM observers_id_seq) as observers_id_seq; 2. Would you also confirm that the Agents in question show connected or disconnected? If they are disconnected, confirm we have attempted to re-register the Agent to Server using the --agent-id XYZ parameter?   Also wanted to share some thoughts related to other comments above: - "Token expired logs seen" - these are probably just from the front end's natural token expiration / refresh and are beguine. Agent tokens do not expire. - "Losing Components etc" - as long as the Agent is not "unregistered" the related Components and data would not be lost. If an Agent does somehow lost connection (as we are investigating here) one thing to try is go to the Agent and use the CLI "disconnect" and "register" using the --agent-id parameter to reregister the existing Agent and attempt to re-establish   ... View more

Hi, Most likely the second site is being identified as a "duplicate". At 2024.1, this is done by evaluating an identifier added to the ArcGIS Server properties config. Please check both servers and see if they somehow match. If they do, the property can be removed from one of the Servers and re-registered with Monitor. See below reference in the documentation: https://doc.arcgis.com/en/monitor/latest/get-started/windows/register-arcgis-server.htm#:~:text=The%20monitorSystemId%20field%20is%20added%20to%20the%20Server%20Properties%20object%20and%20contains%20a%20unique%20identifier%20for%20the%20ArcGIS%20Server%20site. ... View more

Hi @SGTomlins  That particular metric is instrumented within ArcGIS Server itself, which ArcGIS Monitor directly acquires via ArcGIS Server usage reports. Monitor does not perform any additional aggregation at the service level. ... View more

Hi folks, The dev team took a look at this and there is a bug related to the hashed value added to the X-esriHook-Signature header.  For future reference, it should be a sha256 as Kevin described above. Definitely a bug. We'll address this in the next release and include documentation how to match on the receiver side (similar to what Kevin originally went with) Very sorry for the confusion here, and thanks,       ... View more