Idea - Include CPU and Memory in Environment Monitoring

Include CPU and Memory in Environment Monitoring

New

Service Center

By including CPU and Memory history graphs , administrators can easily determine if an unresponsive environment is caused by a single front-end server or if all servers are overloaded. This information would allow them to identify the root cause of the problem and take appropriate measures to resolve it.

14 Mar 2023

Daniël Kuhlmann

MVP

Hi,

Just create a support case at OutSystems and request access to AWS Cloudwatch.

Then you can do what you want.

Regards,

Daniel

15 Mar 2023

Mark Kranz

The access to Cloudwatch granted by support includes CPUUtilization but not RAMUtilization.

We recently had a case where memory exhaustion was causing app pool recycling, which led to sporadic spikes in response time as applications restarted. We were able to infer the issue from logs and CPU graphs, and later have it verified via support and have the environment scaled up.

Having access to RAMUtilization metric for the frontend servers (via Cloudwatch or otherwise) would have made it much easier to track down this issue.

20 Dec 2023