Hi Greg,

1)Goto one of your devices you want to monitor (>Infrastructure>Devices) and select its monitoring template (>Monitoring Templates>Device) under Thresholds you can add a MinMax CPU threshold as long as you have a CPU datasource.

2) I wouldn't necessarily recommending dropping information events; you set it so that information events get aged really quick in (>Advanced>Events).
If you really insist on dropping all information severity events then you could goto (>Events>Event Classes>"Gear Icon">Transforms) and drop in some code to perform a transform, something like:

if evt.summary.severity=2:

      evt._action = "drop"

3) First, make sure you have Zenoss to point to your mailserver (>Advanced>Settings>SMTP Host),then makesure your account email is added in and tested (>Advanced>Users>"Your Account"); lastly you will need to set a trigger and a noftication, and then be sure to link them(>Events>Triggers&>Notifications). When creating a trigger you can set it to trigger on any critical or what-not.

I recommend referring to the Administration guide (below) as it covers these topics pretty well, if something doesn't quite make sense in the Admin Guide, feel free to post a question.

community/documentation/official_documentation/zenoss-guide

Lets say I wanted to create a threshold for memory below 5 percent for all SNMP windows servers (>Infrastructure>Devices>/Server/Windows/"Any windows machine"). Once you are in one of your windows server's you are going to (>Monitoring Templates>Device(/Server/Windows)); on the left you will see current thresholds and you can add your own; the changes you make here are global across that template, if you want another server to have different alerts, you can select the gear icon and create a local template.

Additionally you can go to Advanced, Monitoring Templates to see and change the monitoring templates directly.

Please see 6.2.7.2 - Adding Thresholds (pg71-72) in the Administration Guide for more details and examples.

Based off the 2nd screenshot what you need to do is set the minimum value to:

here.hw.totalMemory / 1024 * 0.05

And you should be good.

memAvailReal is a raw value for memory left in KB (perhaps bytes? cant remember off the top of my head...lol) but its not a nice percentile value like CPU usage, so all we do is do the calulation of what 5 percent is as a raw mem.

This transform should provide a reasonable example on how to convert the raw value into a percentile via a transform for your event messages.

docs/DOC-2449