Logging

Logging overview for FortifiedID EID Server.

EID Server produces two distinct types of logs:

System logging — application and infrastructure events written by the server process
Event logging — structured audit events in CEF format, written by the CefEventModule

Both are controlled by config/log4j2.xml. Log4j2 monitors this file every 30 seconds and reloads it automatically when it changes, so log levels and appender settings can be adjusted without restarting the server.

Log streams

EID Server defines four log appenders in the default configuration:

File	Content	Rolling
`logs/server.log`	Application system log	Daily
`logs/event.log`	CEF audit events	Daily
`logs/network.log`	HTTP access log	Daily
`logs/db.log`	Database activity	Daily

Container behaviour

When the container is started with the -c flag, all log output is routed to stdout. This is the recommended approach for container deployments — use the container runtime's logging driver or a log collector to capture and forward the output.

Quick log level override

The SERVER_LOG_LEVEL environment variable sets the verbosity of the main application logger at startup without editing log4j2.xml. Valid values are TRACE, DEBUG, INFO, WARN, and ERROR. The default is INFO.

podman run -e SERVER_LOG_LEVEL=DEBUG ...

For finer control, edit log4j2.xml directly. See System logging.

In this section