Archiving Alerts (Monitoring Java EE Components)

Monitoring Java EE Components

Archiving Alerts

You can archive the alerts in Enterprise Manager's embedded database. The archive process writes the alerts to .csv files in the JavaCAPS-install-dir/emanager/EventRepositoryDb directory.

The eventdb_archive.properties file in the JavaCAPS-install-dir/emanager/server/shared/classes directory enables you to configure the archive process. The following table describes the properties.

Table 1–2 Alert Archive Properties


Property	Description
GROUP_MAX_COUNT	A group is a set of alerts that have the same values for the following fields: Environment, Physical Host, Logical Host, Server, Deployment, Component, and Message Code. This property specifies the maximum number of alerts that can be in a group. When the number is exceeded, the oldest rows exceeding this number are archived. If the value is 0, then the archive process ignores this property.
MAX_TIME_DELTA_FOR_ARCHIVE	The maximum amount of time (in milliseconds) that can elapse between archive operations. If the value is 0, then the archive process ignores this property.
MAX_EVENT_COUNT_FOR_ARCHIVE	The archive process is run when this number of alerts is reached. If the value is 0, then the archive process ignores this property.
MAX_AGE_OF_EVENTS	When the archive process is run, alerts that exceed this age limit (in milliseconds) are archived. If the value is 0, then the archive process ignores this property.
MAX_ROWCOUNTLIMIT_IN_ARCHIVE_FILE	The maximum number of records that can be stored in a .csv file. When this number is reached, the archive process creates a new .csv file.

If you change the value of one or more properties, then you must restart the Enterprise Manager server in order for the changes to take effect. See Enterprise Manager Basics.