Event

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.

If you receive an email about an event, but it doesn't appear in the Event Monitor, it's probable that the event has expired because the problem is no longer occurring. In order to see problems that occurred in the past, but may not be occurring now, you need to also view the expired events by unchecking the "Open Events" option.

Every engineer and manager who receives alerts from automated monitoring systems can relate to both the critical need they fill and to their often annoying short comings. I'm not just referring to a situation where the monitoring has recently been installed, and you haven't tuned the default thresholds to limit notification to actionable events. The nature of monitoring and alerting, even with the most sophisticated programs, is that problem events are based on very narrow criteria, like a server's CPU Load, or a router's bandwidth consumption, or some application's .NET errors.

If you have SQL Server configured to use all available server memory and do not want Longitude to alert you about low free memory, you can set the MemFreePctMin rule property to zero (0) for the SQLServer, SQL2005, and Windows applications. This can be configured at the computer level using a specific value for the rule properties.

The Event Shutoff section in the Event Details in the Event Monitor can be used to Disable an event indefinitely, or Suspend the event for up to 24 hours. Disabled/Suspended events have the following features:

• The Disabled/Suspended status will only effect the specific EventName/Measured Object/Computer that was selected. That is, if a Service Down alert is disabled for the Syslog service on computer Windows.test.net, it will not stop Service Down alerts from being created for other services or for other computers.

If you have a known period of high resource usage for a device, and would like to delete Longitude events during that period, you can use a Delete action in a Longitude Action rule to remove the Events from the Event Monitor before they trigger any other actions. For example, deleting high Disk IO events for a backup server from from 3-5AM daily.

To set this up:

1. Create an Action rule
2. Select the Event that you would like to delete, and the monitored device or devices