Logging > Event Logging Services

Event Logging Services

The services performing CygNet logging functions are the Event Logging Service (ELS) and the Alarm Event Logging Service (ELSALM). An ELSALM service is an instance of an ELS service.

ELS

The Event Logging Service (ELS) is the CygNet Software service that maintains a journal of system events by logging system-generated events and user-defined events. There are four types of events: service, operations, alarms, and external.

By default, all services (except CAS and GNS) log to the ELS, which logs events.

ELSALM

The Alarm Event Logging Service (ELSALM) is an instance of an ELS. Its purpose is to store alarm and notification events. It can be used to help you occasionally clear out the ELS without losing alarm history.

By default, the CAS and GNS services log to the ELSALM, which logs alarm events. Alarm event types can be alarms or notifications. Alarm history and notification history are also logged to the ELSALM. See Alarm History in the Alarms section for more information.

Note: Alarm history and notification history items are not events, they are data. This means you cannot configure how this information is logged. You can, however, configure the number of days the ELSALM retains the data, just as you can configure how long the Value History Service retains historical data.

ELS Retention Periods

The number of days the ELS or ELSALM retains logging information is a configuration parameter of the designated logging service, where the number of days can be specified.

See ELS and for ELSALM in the Service Configuration Keywords section for more information about the retention period keywords.

ELS Database Size

An ELS database can become quite large in a short amount of time, depending upon what types of events are logged, what file limits are set, and what length of retention period is specified.

To control the database size, you could log only critical event types to the ELS and set the retention period to an acceptable number of days to suit your system constraints. You could then choose to log additional event types to the service log files to reduce the burden on the ELS.

Note: Data logged to service log files in this manner would not be available through CygNet Explorer but could be accessed via the service.

Example

Log only EXCEPTIONS to the ELS, and log CONTROL, EXCEPTIONS, and WARNINGS to the service log file.

To address questions or circumstances beyond the scope of the CygNet Help, Additional CygNet Resources are available.


More:

Back to top

Let us know how we can improve this topic.

CygNet at weatherford.com

© 2020 Weatherford. All rights reserved.