False Alert

Longitude works by collecting a specified set of data for each Application you configure. After the data is collected, it is evaluated and Events are created if the data does not meet specified thresholds. For example, the Windows Application will collect CPU data, and Events will be created when the CPU usage on a device is too high.

These Events are visible in the Event Monitor, and can be used to trigger Action Rules or Correlated Events that will send notifications for the problems via email, text message, pager message, SNMP Trap, or will execute an OS command.

A more efficient ping was introduced for version 6.2. If you do not wish to upgrade these are the steps to implement it.

1. Grab the patch (Right Click Save Target As)
2. You will need to stop your Longitude Services from Services.msc
3. Place the files in the patch into the following directories Longitude\common\lib\firenze-common.jar
   Longitude\dc\lib\firenze-collectors.jar
4. Start the services back up
5. The ping fix is now implemented