Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We are using EC2 instances and are monitoring the server usage.

Right now the main metric we are looking at is idle CPU: Monitoring load on AWS EC2

However, I am also hoping to monitor "load" as measured by the top command. We are running on large instances, so it appears to us as if we have 2 cores.

For fully owned servers, I usually set the trigger value to slightly higher than the number of cores (e.g. if 2 cores, trigger an alert if the load is over 2.5 for more than a minute). Is this still the right thing to do on EC2?

share|improve this question
up vote 0 down vote accepted

After finding out that load measures correctly for each user on EC2, we went with our standard load triggers.

For us that is half a CPU above the max for more than 5 minutes.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.