Latest Contributions by AndrewSakowicz

please ensure these host addresses are exactly as registered in monitor.  We can validate it, if can share redacted screenshots of ArcGIS Monitor registered hosts and the below config?    ... View more

Thank you for this info.  These expressions are OK.  These gaps are expected behavior when components are not reachable (return null data).  Any chance some of these machines where restarted around 8:35 or re-registered? We will evaluate new charting options and see if instead of these gaps, the bar could be compressed.    ... View more

Thank you! ... View more

Please include expression. ... View more

The host CPU looks OK.  The process CPU spike (single value) appears to be some sort of edge condition with WinRM reporting for this particular process counter case.  Is this spike just for arcsoc.exe process?  How often does it happen, 12 hours?  In any case, thank you for reporting it. We'll keep an eye on this and if able to reproduce, try to address it.  ... View more

Agree, cpu process > 100% does not make sense.  And we've seen this occasionally. However, ArcGIS Monitor process reports windows api results.  So there might a problem with windows reporting.  FYI, 10.8 we capped the reporting to 100%, therefore you would not run into this case.  In any case, this stat points out high activity by one or several arcsoc processes.  Can you share CPU utilization on this host for the corresponding time.  Also, do you see a particular arcsoc process that is using high cpu? @EsriEvan @GeoJosh  ... View more

Although as  @DerekLaw  pointed out, data store is not a supported component, users can potentially monitor availability using combination of host, db components and server logs.  Note, ArcGIS data store does not have a direct "health check" call.  ... View more

@Fabio_Pires This issue is fixed and uploaded. Please download the latest.  Note, this is a sample code and not part of the product. ... View more

I will contact you directly. ... View more

Thank you for the info.  Very helpful.  It appears, this condition impacts min 3 requests and lasts approximately 15 min, (3 points above, with 5 min interval).  If you change the alert sample from 3 to 5 (and potentially change aggregation to p95) the alerts will not fire for the above. ... View more

What is  the performance of the "first time hit" vs. the consecutive?  Are these "first time hit" alerts valid? Is the challenge there are many alerts in the UI ?    ... View more

@MKR , Of course, we'll announce shortly once the doc is updated.  The UI for partition retention will be under Administration>Database.  This feature is scheduled to be part of 2023.2, June 2023.  So please allocate disk space for the next 2-3 months.  In your case, it might be additional 300-400 GB.  If provisioning this disk space is an issue, please let us know.  We can walk you through how to do this manually: this feature frees up disk space by dropping PostgreSQL older partitions in metrics_data table.   ... View more