I agree 100%
Currently we are dealing with service interruptions and downtime and find myself pouring over hard to decipher logfiles and trying to understand what the issue is for each error. Why isn't this incorporated into the software to detect the issue and report it in a more readable, identifiable, and potentially self-correcting manner? I'm seeing SEVERE errors in our logfiles for clients trying to reach a service that has been deprecated for YEARS. Why can't ArcGIS Server identify these legacy services and isolate them to another bin. I don't need them in the logfile.
Similarly, if a particular service is experiencing timeouts, isolate it, recycle it, and if it continues, provide better reporting. Instead, we're forced to license a separate product for service monitoring which should be included as value-added functionality to ensure uptime.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.