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.
