On premise Airwatch guys!
WE are on premise (Version 19.07) and our servers often fail with lots of performance RAM/CPU issues. WE have 50k devices enrolled (4 DS and 2 console server)
We are having to reboot our VM's daily and do frustrating IIS resets.
Is there a tool which sends out sms or email notifications if there are performance issue seen?
Also, when the private Que goes over a certain limit, can we automatically trigger a reboot?
We use SolarWinds. You can probably setup some fancy monitoring using it. Or if you are so inclined use some powershell scripts to check these things as well.
Also seen Nagios - The Industry Standard In IT Infrastructure Monitoring before and that was nice as well.
I am experiencing similar issues. We are also On-prem(1907) and have over 31K devices with 2 DS and 2 CS. IIS worker process kept using more than 95% CPU and memory. High usage choked the hub app. It would not launch. IIS resets and server reboots helped but did not fix the issue. Vmware support could not find the root cause but suggested to add more CPU and memory. That fixed the IIS issue for us. No spikes in last 3 weeks. We are working on adding another DS and probably update to 2001 soon.
Look at the architecture guides and make sure you are spec'ing your servers properly. It really makes a difference. Also make sure Windows is configured to handle the load with Virtual Memory settings, etc. If these are virtual servers (VMware, azure, etc) make sure they are also tuned to work with high pressure situations.
Not a whole lot. Just basics. CPU usage, disk usage, etc. Haven't found a need to go much further as I haven't seen performance issues. Are you using Cache servers? Memcached is recommended for large deployments.
We also had memory leak issues with previous versions of Workspace ONE (AirWatch).
To protect the service we implemented IIS App Pool memory limits. This will recycle the IIS App Pool and prevent server memory saturation. Maybe also look a CPU limit also.
This is a MS SharePoint link but gives you the instructions.
Also check your logging levels. If you have any always set to Verbose that will cause CPU/Memory issues as the log files are generated and written.
We have 35k devices with 4 DS and 2 CS servers. Each server is Windows 2016 VM with 6 CPU/12 GB RAM. We don't see any performance issues on 19.09.07.