Avaya Breeze® platform log service

Last Updated : Nov 20, 2019 |
Prolog information
Metadata
Keywords:
Avaya Breeze® platform provides the following log service enhancements:
  • The logs for snap-ins are available in the /var/log/Avaya/services/<ServiceName>/<ServiceName>.log file. The log files of all the versions of the snap-in are available in the <ServiceName> directories. The logs are present on the Avaya Breeze® platform node and not on System Manager.
  • The maximum size of the service logs is controlled by the snap-in. You can view the maximum log size for a snap-in on the Service Management page for that snap-in.
  • Each log message contains the full class name from where the log was generated, the snap-in name, and the snap-in version details.
  • The log files from the 3.0 version of the EmailConnector, the SMSConnector, and the ScopiaConnector use the Avaya Breeze® platform logger instead of the Avaya common logger. The connector and the mandatory services provided by Avaya Breeze® platform use the Avaya common logger.

Log levels

Avaya Breeze® platform logger provides various log levels to indicate the severity of the log messages. The following table specifies the possible log levels in Avaya Breeze® platform:
Log level
Description
Fatal
Indicates a very severe event that might cause a service to fail.
Error
Indicates a serious error, but the service might continue to function.
Warn
Indicates the possibility of a harmful problem, but the service continues to function.
Info
Indicates an information message.
Fine
Indicates a message of finer granularity than an information message.
Finer
Indicates a message of finer granularity than Fine.
Finest
Indicates a message of finest level of granularity.

Log service commands

Use the /opt/Avaya/contrib/bin/ce tool that is present on the Avaya Breeze® platform node, to enter commands for viewing logs and changing logs configuration. The commands have been enhanced to take a snap-in name as an argument so that the action is only on the log files of that particular snap-in. For example, ce dlogstat <snap-in name>.
Caution:
Use the ce dlog command with caution. This command is performance impacting.
You must view the logs on the server if you are using the log service commands tool.
Command
Description
dlogstat <snap-in name>
Displays the status of the log including the files and the size.
dlogc <snap-in name>
Displays all the snap-in’s log files
dlogt <snap-in name>
Displays the reverse line snap-in’s log files
dlogv <snap-in name>
Displays the snap-in log files in the vi editor.
dlogw <snap-in name>
Watches or tails a snap-in’s log files. New contents in the log file are printed on the screen.
dlogwi <snap-in name>
Watches or tails a snap-in’s log files immediately.
dlogwf <snap-in name>
Tails a snap-in’s log file into X.log as well.
dlog4j <snap-in name>
Displays the snap-in’s log4j.properties file and the definitions of the properties.
dlog4jc <snap-in name>
Displays the snap-in’s master file, the file used after restart.
dlog4jm <snap-in name>
Displays the snap-in’s master file.
dlogclear <snap-in name>
Clears the rolled-over logs, except the active log.
dlogon <snap-in name> <arg>
Turns on the finest debug level for the snap-in logs. You can add the logging level as the argument. The debug level will be enabled for the log level you set.
dlogoff <snap-in name> <arg>
Reverts to the default debug level for the snap-in logs. You can add the logging level as the argument. The debug level will be disabled for the log level you set.
Related links
Log files
Modifying the logging configuration