ArcGIS Monitor Registering Agents in an Autoscaling Environment

Question

We used the Esri CF template to deploy Enterprise 10.9.1 in AWS with autoscaling. Have been using Monitor for some time. Upgrading to 2024 recommended installation of Agents on all nodes. All the nodes in our deployment contain the same Windows host name. When attempting to register multiple existing ArcGIS Server nodes, we receive an error stating that "unique validation failed on name" (see attachment). To be clear, the Agent is installed on the node it just can't be registered with Monitor Server. How can we accomplish this? Is this expected behavior and seamless?  Also, is there anything that should be done to ensure Monitor will work with nodes that are created from a scale out event? Thanks. @DerekLaw

monitor-error.gif

highlights.png

DerekLaw · Answer

Hi @NCOneMap,

I appreciate you sharing the additional context. Please contact your Esri account manager/tech advisor and let's try and schedule a meeting so I can learn more about your requirements. Or you're welcome to email me directly (dlaw@esri.com) and we discuss this item more.

Hope this helps,

NCCGIA · Answer

Thanks Derek. I would like to provide a bit more context and info about our situation just in case it isn't part of, or being addressed, by the remediation of the existing bug.

As I mentioned, we have Enterprise in an AWS autoscaling environment. Therefore, instances come and go base on system load. As these scaling events occur, one of the instances that may be terminated could be the one whose IP address is registered as the Monitor Agent. How can we ensure that there will always be a valid server to assume Monitor Agent responsibilities? Our thinking is that as soon as a new machine comes online, we would immediately transfer Agent responsibilities to it. However, how do we deregister the existing agent as the new one comes online? Based on the commands found on the Manage Monitor Agent machines web page, all of these commands are local to the machine. The conundrum is how to accomplish all of this in an automated fashion.

Hopefully, we're missing something, making this more complex than it really is, or that Esri working on a solution as part of the aforementioned bug. Any guidance would be greatly appreciated.

DerekLaw · Answer

Hi @NCCGIA,

> To be clear, the Agent is installed on the node it just can't be registered with Monitor Server. How can we accomplish this? Is this expected behavior and seamless?

I believe this behavior is related to a known bug in ArcGIS Monitor 2024.x,

BUG-000176010 - Agents on AWS can fail registration due to duplicate address.

I'm sorry for the inconvenience. The team is actively working on addressing this for a future release. Please open an Esri Tech Support issue and you can attach the behavior you're seeing to the bug. This will help prioritize it.

Hope this helps,