Check which is specific to the agent only.

For some reason (memory according to Tim) logstash is going down and checks are not detecting this due to the logstash web process still running. This makes the check more specific to check the agent is up.

If we still want to check for the web we can bump the process count and
have the less specific check or we can create a separate check.
Require virtualenv_path param for all python_app resources
Merge pull request #680 from alphagov/fix-virtualenv-path

Require virtualenv_path param for all python_app resources
Merge pull request #679 from alphagov/check-for-logstash-agent-not-web

Check which is specific to the agent only.
Fix for no alerts even when logging drops to 0

The ruby check uses < or > not >= or <=. Checking below not below zero
makes not sense.