Event Monitor

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.

When a problem appears on the event monitor and you select it a blue bar appears in the middle of the screen which gives you the option to send out an e-mail. This is useful for letting others know that a problem exists and could be utilized to ask someone a question based on the alert. (e.g. what would an appropriate threshhold be for this issue.)

The Manage Monitoring display shows that status of collections, not the results of those collections. Since the Statistics Server is successfully running the "Ping", "PingCritical", etc. test, the icon is still green, because you're able to run the transaction test. Any failures for transactions will create Longitude events, and these events can be viewed in the Event Monitor.

The Unix memory collector for Linux runs free -k to collect data. The output of this command looks like:

You receive the following error message from the Event Monitor:

SQL Statement is too long. Increase the DB parameter Packet Size.

Please follow these steps:

1. Stop all of the Longitude Services (Statistics Server, Consolidator, Engine, WebUI, Upgrade Manager)
2. Log into the following url:
   http://LongitudeServerName:7230/webdbm
   Database: FZEDB1
   User: dbm
   Password: the password entered when install was done
3. Under Configuration click Parameters

1. Set up WindowsEventLog Monitoring.

   By default, only Error messages are collected from the Application and System logs. Configure additional collections to collect other severities or logs.

2. Viewing WindowsEventLog Events.

   Visible in Dashboards >> Event Monitor >> WindowsEventLog. Please note: Only events in the Application view can be used to trigger action rules or correlated events.

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.