Tailoring custom thresholds

Longitude rules can be configured with Entity-Specific threshold settings. For example, setting the DiskFreeCriticalPctMin for the D: drive on a computer to use 5% while all the other drives use the default 10% value. This is done through Monitoring --> Manage Rules --> {Application} --> {Task} --> Click on "Add" or "Modify" to adjust thresholds (it will be Add if everything is using the default value, and Modify if something has been customized).

In the Specific Values screen for the threshold, select the checkbox for the entity or entities you want to modify, type a value in the "Value" field, and then click on "APPLY". The next time the rule runs, it will use the threshold specific to it. If you have a custom threshold set, you will also see a "RESET TO DEFAULT" button to allow you to back out of a customized threshold.

If you would like to change the default value used by a rule, change it in the main Monitoring --> Manage Rules --> {Application} --> {Task} screen, and any entities set to use the "default" value will now use the updated default value.

After Longitude has started collecting data for an application, you can view baseline values in the Rules screens as well - to the right of the Value box in the Manage Rules and Add/Modify screen is a gray triangle - click on the triangle, and the Web UI will display the minimum, maximum, and average values for the metric being monitored. The longer Longitude has had to collect, the more accurate the baselines will be, but, at a minimum, they will be displayed after one collection interval. The interval depends on the collection being made - for example, the Windows CPU metric is collected at a 5 minute interval, while Windows Disk data will take an hour.