Configuring Logging

Logging is configured on a per service basis for each CygNet service, by setting the values of several keywords in its service configuration file. Some logging options can also be entered via command-line parameters.

Service Configuration Files

The service configuration file (Service.cfg) for each service is located in the CygNet\Services\Service folder on your host server. In the file, use the following keywords to define logging for your service.

Associated Services ELS Keyword

Keyword	Definition
ELS	The Site and Service name of the service’s ELS, in Site.Service format.

Use this keyword value to specify the ELS or ELSALM to which log files for your service will be written. Type in the desired ELS Site and Service name, in Site.Service format, and save the file.

Note: The logging keyword that defines the logging retention period (the number of days an ELS retains logging information) is a configuration parameter of the associated ELS, and is specified within that ELS service configuration file. See the Retention Period Keywords for ELS and for ELSALM for more information.

Other Logging Keywords

Logging keywords include LOGMASK and LOGFILE types. Use these keywords in conjunction with one another to specify logging behavior for the selected service.

LOGMASK Keywords

The LOGMASK keywords define what types of events are written to the designated logging service and to the service log files.

For each LOGMASK keyword (LOGMASK_ELS or LOGMASK_FILE), use the following values to specify the type(s) of information to log to that location. Valid keyword values can be used alone or in combination.

Keyword	Definition
LOGMASK_ELS	Specifies the types of service events to be logged to the associated ELS (specified in the ELS keyword). To disable logging to the ELS, comment out the ELS keyword for the selected service. See the Note below this table for more information about the keyword values. See LOGMASK_ELS in the Logging section of this Help for more information. The LOGMASK_ELS ( LMask ELS) info item will report the value of this keyword.
LOGMASK_FILE	Specifies the type(s) of service events to be logged to the service’s log file ([file name].log). During the current session of the service, data is written to the current log file. Log file names follow the naming convention of the selected logging mode (as set by the LOGFILE_MODE keyword value). See the Note below this table for more information about the keyword values. See LOGMASK_FILE in the Logging section of this Help for more information. The LOGMASK_FILE (LMask File) info item will report the value of this keyword.

Note: Use the following keyword values to set logging options for the LOGMASK_ keywords.

LOG_ALL - logs all options. This is the highest level of logging and will log everything the service is programmed to log.
CONTROL - logs control operations, such as startups, shutdowns and UIS operational events, etc.
ENTER_EXIT - logs every entry and exit through functions. This is used primarily by a programmer to debug code, and is too verbose for the ELS (not applicable for LOGMASK_ELS).
EXCEPTIONS - logs all exceptions thrown, not all of which are severe. An exception is an unexpected event occurring during execution of the service. It could be the result of a configuration error, an invalid command parameter, a bug, etc.
MAX_TRACE - more verbose logging than MIN_TRACE. This is used primarily by a programmer to debug code, and is too verbose for the ELS (not applicable for LOGMASK_ELS).
MIN_TRACE - used primarily by a programmer to debug code.
PROG_STAT - typically used to monitor the progress of the code through some logical steps. Some services, like the GNS, use it to add to the logging of the notifications, acknowledgments, and operations.
STATISTICS - enables gathering and reporting of message processing statistics.
WARNING - logs anomalies, not as serious as exceptions.

A value for LOGMASK_FILE might be CONTROL + EXCEPTIONS + WARNING + PROG_STAT.

LOGFILE Keywords

The LOGFILE keywords work together to define the way log file sets are maintained by the service.

Command-Line Parameters

Use the following standard command-line parameters to control log file creation.

The following standard command-line logging level parameters can also be used to define log file content.

Keyword	Definition
LOGFILE_FILE_COUNT	Specifies the maximum number of log files that a service will create before it starts re-using log files. For example, a count of two will produce SVC001.log, then SVC002.log, and then start back at SVC001.log, where SVC is the name of the service. Specify any value from 2 to 100. See LOGFILE_FILE_COUNT in the Logging section of this Help for more information. The LOGFILE_FILE_COUNT (File Cnt) info item will report the value of this keyword.
LOGFILE_FILE_SIZE	When the value of the LOGFILE_LIMIT_MODE keyword is set to SIZE, this keyword specifies the maximum size (in megabytes) allowed for a log file, before logging will be continued using the next log file. Possible maximum size values are user-determined, respecting the limits of your specific system configuration. The default value is 100 megabytes. When the specified limit is reached, the log finishes the current line, closes the current file, and then continues logging in the next available log file. See LOGFILE_FILE_SIZE in the Logging section of this Help for more information. The LOGFILE_FILE_SIZE (File Size) info item will report the value of this keyword.
LOGFILE_LIMIT_MODE	Specifies how to limit the size of each individual log file. Options are LINE (maximum line count is determined by the LOGFILE_LINE_COUNT keyword) or SIZE (maximum file size in megabytes) determined by the LOGFILE_FILE_SIZE keyword). The default value is LINE. See LOGFILE_LIMIT_MODE in the Logging section of this Help for more information. The LOGFILE_LIMIT_MODE (Limit Mode) info item will report the value of this keyword.
LOGFILE_LINE_COUNT	When the value of the LOGFILE_LIMIT_MODE keyword is LINE, this keyword specifies the maximum number of lines per log file. When the specified line count is reached, the log file is truncated at the limit point, and logging is resumed using the next available log file. Specify any value from 1000 to 1000000. See LOGFILE_LINE_COUNT in the Logging section of this Help for more information. The LOGFILE_LINE_COUNT (Line Cnt) info item will report the value of this keyword.
LOGFILE_MODE	Specifies the operational mode for the log file, that is, how log files are maintained. Options are LEGACY or EXTENDED. The default value is LEGACY. See LOGFILE_MODE in the Logging section of this Help for more information. The LOGFILE_MODE (Logging Mode) info item will report the value of this keyword. LEGACY In LEGACY mode two log file sets are maintained: the current log file set and the previous log file set. When a service is stopped and restarted, a new log file is generated and log files from the previous session are renamed as follows: The current log file is named Service001.log (for example, UIS001.log) and is populated up to the LOGFILE_FILE_COUNT and configured file limits (the value of either the maximum LOGFILE_LINE_COUNT or LOGFILE_FILE_SIZE, as determined by the LOGFILE_LIMIT_MODE value.). The previous log file set is renamed by prepending the file name(s) with a tilde (for example, the previous UIS001.log becomes ~UIS001.log). Once another service restart occurs, these tilde files are no longer maintained, and are replaced by the subsequent file set. EXTENDED In EXTENDED mode multiple log file sets are created and maintained: the current log file set and multiple previous log file sets, up to the limits specified by the LOGFILE_FILE_COUNT and either the LOGFILE_LINE_COUNT or LOGFILE_FILE_SIZE keywords. When a service is stopped and restarted, the most recent log file is opened to resume logging with current information. A new log file is created only when the LOGFILE_LINE_COUNT or LOGFILE_FILE_SIZE for the file is exceeded, as follows: The current log file is named Service.log (for example, UIS.log) and is populated up to the value of either the maximum LOGFILE_LINE_COUNT or LOGFILE_FILE_SIZE, as determined by the LOGFILE_LIMIT_MODE value. Previous log files are renamed Service001.log, Service002.log (for example, UIS001.log, UIS002.log), and so on, up to the LOGFILE_FILE_COUNT limit, with the highest number assigned to the oldest log file. Once the LOGFILE_FILE_COUNT limit is exceeded, the oldest log file is overwritten.