I am seeing some critical alerts in ArcGIS Monitor 2025.x that show several services are at 100% instance saturation. However, these services are configured to use the shared instance pool.
Does this mean that the shared instance pool is maxed out? Or is it just a false alarm?
Solved! Go to Solution.
Hey @MichaelJenkins
It appears that this is currently a bug, here is a link to a post that I had commented on in the past: https://community.esri.com/t5/arcgis-monitor-questions/monitor-2025-0-shared-instance-saturations-at...
The content:
It appears that this is a bug according to this post: https://community.esri.com/t5/arcgis-monitor-questions/instance-count-for-shared-services-after-arcg...
Here is the slated workaround offered by the answering user:
"
I went into ServerAdmin and just changed the max maxInstancesPerNode value to 1 and left the minInstancesPerNode at 0 and am now getting small percentage sat values (like 0.45, 0.56, etc) for these services in the shared instance:
Configured State
Started
Instance Type
Shared
Instance Limits
0 min - 16 max
"
I would raise an issue with support and bring more attention to this bug as well!
Cody
Hey @MichaelJenkins
It appears that this is currently a bug, here is a link to a post that I had commented on in the past: https://community.esri.com/t5/arcgis-monitor-questions/monitor-2025-0-shared-instance-saturations-at...
The content:
It appears that this is a bug according to this post: https://community.esri.com/t5/arcgis-monitor-questions/instance-count-for-shared-services-after-arcg...
Here is the slated workaround offered by the answering user:
"
I went into ServerAdmin and just changed the max maxInstancesPerNode value to 1 and left the minInstancesPerNode at 0 and am now getting small percentage sat values (like 0.45, 0.56, etc) for these services in the shared instance:
Configured State
Started
Instance Type
Shared
Instance Limits
0 min - 16 max
"
I would raise an issue with support and bring more attention to this bug as well!
Cody
Thank you for the quick response and the helpful information. We have too many services to do a per-service workaround, so I think I will just disable that metric for now. I will open a support ticket to raise awareness and try to get our ticket attached to the BUG, if it exists.