nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Metrics and Alerts on Shared Instances

NickN

I'm new to Monitor and recently deployed the new version to our production environment shortly after release. I'm curious what best practice is, or what others are doing for services that are on the shared instance pool.

It seems whenever one of these services is queried the "Instances Saturation Percent" metric goes to 100% and by default that triggers an alert.

Do most people disable alerting on these, or is there some other way I should be handling these?

Thanks!

Encuentra más publicaciones etiquetadas con

Accepted answers

NickN

Yeah that definitely looks like the issue. I created a new service and configured it to the shared pool in the Share Web Layer pane in Pro and that graph looks like what I would expect:

I also noticed in the Overview screen in the Specifications section the new service it shows 8 in the Instance Limits section:

While all the older services that were switched from dedicated to shared have the Instance Limits blanked out:

And it's only those one's that are blanked out like that where the saturation graph bounces from 0 to 100%. So that got me thinking.

I switched the service back to Dedicated in ArcGIS Server Manager. Waited for the item in ArcGIS Monitor to indicate Dedicated again, then republished it and specified Shared in Pro. Then when Monitor refreshed it showed Shared with Min 8, Max 8 in the specs box as well as showing the correct saturation percent...so there's a work-around to fix it 🙂

Thanks for pointing me in the right direction, @MKR

All comments

GeoJosh

Hello,

I'm curious what ArcGIS Server's "Number of shared instances per machine" setting is currently set to. You can check this by signing into ArcGIS Server Manager > Site > Settings.

The default is 4 and when I query a service that is set to "Shared", the "Instances Saturation Percentage" metric in Monitor reflects between 15% and 30% which is what I would expect. If you are seeing that this metric is spiking to 100% every time a service is queried, this may be a sign that it should be increased.

Josh

NickN

Hi Josh,

Our shared instances is set to 8, and we just have a single machine site. Maybe I'm just coincidentally viewing it when all instances are handling active requests (which may include other services in the pool)

This is what the graph looks like for a service that's in the shared pool:

As you can see it's always bouncing from 0% to 100%

MKR

Hi Nick,

I am guessing that is a shared instance percent of one particular service?

An alternative to increasing the number of shared instances would be to try to switch the service to dedicated, especially if its a service that is used a lot and you don't want the initial start-up lag then set it to 1 and 2 and review again the next day (note: services set as dedicated and 1 minimum will always be running and consuming resources on the server).

In our environments I have created a graph showing all instances that are spiking to 100% use and review this regularly.

What version of enterprise are you on? 10.9.1?

NickN

Yeah I'm on 10.9.1.

This seems to be the case for any service on the shared pool. I ran into this as I was attempting to move some infrequently used services into the shared pool. The documentation suggested that good candidates were: "for most deployments, this means fewer than one service request per minute on average." So that's what I started with when I ran into this issue.

For example the two charts below are for a single service in the shared pool. You can see the smaller spikes around 7:50, 8:00, 8:30, 8:35 all were where 2 requests were received, yet the instance saturation at the same time was 100%.

Basically I never see a saturation percent at any value other than 0 or 100 on a service in the shared pool.

AndrewOrton

This was logged as BUG-000157186, and has been fixed in ArcGIS Monitor 2023.2.

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Iniciar Sesión
Registrarse

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.