Logback Logging — Configure MideyeServer Log Management

MideyeServer uses Logback for all application logging. Logback is a flexible, high-performance logging framework that supports multiple output destinations (appenders), configurable log levels, and automatic file rotation.

All logging configuration is controlled by the logback.xml file, which can be edited directly on the server. Changes to logback.xml are automatically detected and applied without restarting MideyeServer (via the scan="true" attribute).

---

Configuration file locations

The logback.xml configuration file is located in the server’s config directory. The exact path varies by platform:

Platform	Configuration File Path
Debian / Ubuntu	/opt/mideyeserver6/config/logback.xml
RHEL / Rocky	/opt/mideyeserver6/config/logback.xml
Windows	C:\Program Files (x86)\Mideye Server 6\config\logback.xml
Docker	Mounted at /opt/mideyeserver6/config/logback.xml

Tip

On Linux systemd-managed installations, the logback configuration file path is explicitly set via JVM arguments in the service file:

• -Dlogback.configurationFile=file:/opt/mideyeserver6/config/logback.xml
• -Dlogging.config=file:/opt/mideyeserver6/config/logback.xml

---

Default log files

MideyeServer writes to two log files by default:

Primary application log

File: mideyeserver.log

Contains all INFO-level and higher log events from the entire application, including:

• Startup and shutdown events
• RADIUS authentication attempts
• Configuration changes
• Database operations
• All application components

This is the primary log file for troubleshooting and monitoring.

Error log

File: mideyeserver.error

Contains only WARN-level and higher log events from MideyeServer components (com.mideye.* loggers). This filtered log makes it easier to identify problems without sifting through informational messages.

Both log files use the same format and rotation policy.

---

Log file locations

Log files are written to the server’s log directory:

Platform	Log Directory	Environment Variable
Debian / Ubuntu	/opt/mideyeserver6/log/	LOG_PATH (systemd)
RHEL / Rocky	/opt/mideyeserver6/log/	LOG_PATH (systemd)
Windows	C:\Program Files (x86)\Mideye Server 6\log\	MIDEYE6_LOG_PATH
Docker	/home/mideye/log/	Spring property

Note

The log path is configured via the Spring property application.log-path in application-prod.yml for most platforms. Windows uses the MIDEYE6_LOG_PATH environment variable set by the installer.

---

Log format

All log entries use the following pattern:

%date{yyyy-MM-dd HH:mm:ss.SSSXXX, UTC} %-5level [%thread] %logger{0}: %msg%n

Example log entry:

2026-02-25 14:32:15.847+00:00 INFO  [main] MideyeServerApp: Application 'MideyeServer' is running!

Format breakdown:

Component	Description	Example
%date{...}	Timestamp in UTC with timezone offset	2026-02-25 14:32:15.847+00:00
%-5level	Log level (left-aligned, 5 chars)	INFO , WARN , ERROR
[%thread]	Thread name	[main], [http-nio-8080-exec-1]
%logger{0}	Logger name (abbreviated)	MideyeServerApp
%msg	Log message	Application 'MideyeServer' is running!
%n	Newline

Tip

All timestamps are in UTC to avoid confusion in multi-timezone deployments. The XXX format includes the UTC offset (+00:00).

---

File rotation policy

Both mideyeserver.log and mideyeserver.error use a size-based rotation policy:

• Max file size: 10 MB
• Policy: FixedWindowRollingPolicy
• Rotated files: mideyeserver.log.1, mideyeserver.log.2, etc.
• Compression: Not enabled by default (can be configured)

When a log file reaches 10 MB, it is renamed to .1, the previous .1 becomes .2, and a new empty log file is created. See Log Rotation for customization options.

---

Container logging

When running MideyeServer in Docker, the STDOUT appender output is captured by the container runtime’s log driver.

Default behavior:

• Docker captures STDOUT and writes to the JSON file log driver (/var/lib/docker/containers/<id>/<id>-json.log)
• File-based logs (mideyeserver.log, mideyeserver.error) are written inside the container to /home/mideye/log/

Recommended approaches:

Scenario	Method	Details
Docker standalone	Mount log volume and use file tailing	Mount /home/mideye/log/ to a host path, then use Filebeat or Promtail
Docker with JSON driver	Collect STDOUT via Docker log driver	Configure the Docker daemon’s log-driver (e.g., gelf, syslog)

For STDOUT appender configuration, see Console & journald. For log collector setup, see Log Aggregators.

---

Topics in this section

Log Levels Configure logging verbosity for MideyeServer components and third-party libraries.

Log Rotation Customize file size limits, retention policies, daily rotation, and compression.

Syslog Forward logs to syslog servers using SyslogAppender, rsyslog imfile, or syslog-ng.

Windows Event Log Built-in Event Viewer integration and Windows Event Forwarding (WEF).

Log Aggregators Integrate with Splunk, ELK, Graylog, and Loki for centralized logging.

Console & journald Configure STDOUT logging, systemd journal integration, and journal forwarding.

---

Related documentation

• Log Files: Web-based log viewer for browsing, searching, and exporting log files
• Log Configuration: Runtime log level management and trace logging via the web UI
• Authentication Logs: RADIUS authentication event logs (stored in database, not logback)

---

Access & support

Editing logback.xml requires direct file system access to the MideyeServer installation. Changes take effect automatically within 60 seconds due to Logback’s configuration scanning feature.

For assistance with log forwarding configuration, contact Mideye Support or refer to the examples in each topic page.