# Configure log output for 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.

| Option | Required | Default | Description |
| --- | --- | --- | --- |
| file | no | N/A | Output log file path. Rotated logs are placed in the same folder as this log file. |
| enable-console-logging | no | false | When 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-history | no | 30 | Maximum number of log files to retain. |
| levels | no | N/A | Map from logger name to its log level. Valid log levels are `error`, `warn`, `info`, `debug`, and `trace`. |
| ticker-interval | no | 10 | Ticker log interval in seconds. |
| format | no | simple | Format of the log. See [Logging Formats Section](#logging-formats) for more details. |

## Logging formats

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

| Format | Description |
| --- | --- |
| simple | Simple space delimited format of a log line. |
| json | JSON formatted logs. |

### Example

```yaml
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

```yaml
logging:

  file: /var/log/aerospike-jms-inbound/aerospike-jms-inbound.log

  levels:

    ...

    message-parser: error # Set message parser logs.

    ...
```