Shared service - Instance saturation Percentage Alert

[MichaelBartlett]

I have been noticing occasional alerts on Instance Saturation for some services with Shared Instance pooling.

It is not every service that is using the Shared pooling method.  

The critical level is 100%.  Is this trying to tell me something different than the Services with a dedicate Instance pooling?

[JoeGuziStarkCountyOH]

Greetings,

I have noticed this too. I haven't really had a chance to dig into yet. Everything appears to be working in spite of the critical alert. I guess I just wanted to say that you are not alone. Thank you for everything and have a delightful day.

Sincerely,

Joe Guzi

[Craig_Lunde]

I am also seeing this with shared instances that have 0 min and 0 max in the settings. Possibly a previous bug that is back?

https://community.esri.com/t5/arcgis-monitor-questions/metrics-and-alerts-on-shared-instances/td-p/1...

https://support.esri.com/en-us/bug/critical-instance-saturation-alert-for-services-with-a-bug-000157...

[DavidWittmann]

I'm also seeing this issue with service using Shared instance types where the Instance Limits are being shown as 0 min - 0 max. This seems to cause the invalid triggering of alerts on the Instances Saturation Percent metric which is problematic if you want your Open Alerts to reflect actual potential issues in your system. 
@DerekLaw, is this an issue that will be addressed in the upcoming 2025.1 patch release?

[DerekLaw]

All,

Apologies for the late reply to this thread.

Can you please open a case with Esri Tech Support so they can help investigate further? And hopefully get a repro case with the latest Monitor release. 

We did have an issue with critical instance saturation alert for services with a shared instance type, but this was fixed (as @Craig_Lunde referenced).

> ... is this an issue that will be addressed in the upcoming 2025.1 patch release?

This is not part of the forthcoming ArcGIS Monitor 2025.1 release (it's not a patch). We don't currently have any open issues on this behavior. Please open a case with Esri Tech Support.

Hope this helps,