Skip to main content
Loading

Configuring Log Files for the JMS Inbound Connector

The logging section of the /etc/aerospike-jms-inbound/aerospike-jms-inbound.yml controls the log output for the JMS inbound connector. Log files are rotated daily and, by default, logs are retained for 30 days.

OptionRequiredDefaultDescription
filenoN/AOutput log file path. Rotated logs are placed in the same folder as this log file.
enable-console-loggingnofalseWhen set to true and a log file is specified, logging is sent to both console and the log file. enable-console-logging is false by default but if a log file is not specified, it is forced to true.
max-historyno30Maximum number of log files to retain.
levelsnoN/AMap from logger name to its log level. Valid log levels are error, warn, info, debug, and trace.
ticker-intervalno10Ticker log interval in seconds.
formatnosimpleFormat of the log. See Logging Formats Section for more details.

Logging formats

Logs can be output in one of the following logging formats:

FormatDescription
simpleSimple space delimited format of a log line.
jsonJSON formatted logs.

Example

logging:
file: /var/log/aerospike-jms-inbound/aerospike-jms-inbound.log
levels:
root: debug # Set default logging level to debug.
com.solacesystems: error # Set solace package's logging level to error.

Parsing Errors

To log the messages which could not be parsed set the log level of message-parser to error.

Example

logging:
file: /var/log/aerospike-jms-inbound/aerospike-jms-inbound.log
levels:
...
message-parser: error # Set message parser logs.
...