Detailed Logs configuration reference for DayZ

Configuration file and presets

After installing Detailed Logs as a server mod, start the server once. The mod creates its settings in $profile:DetailedLogs/config.json. The $profile folder is selected with your server’s -profiles launch option.

Use the config.default-basic.json or config.default-all.json preset shipped with your installed mod as a starting point. Keep a copy of your settings before replacing them, and restart the DayZ server after making changes.

Switches use integer values: 1 for enabled and 0 for disabled. Interval and size settings use numbers instead. Use the settings and defaults supplied with your installed mod version.

Core logging settings

Detailed Logs core configuration options
Setting	Purpose
`detailedLogs`	Master logging switch: 1 enables logging, 0 disables it.
`detailedLogsJson`	Use 1 for the JSON event output that DZLoggy reads.
`detailedLogsOverride`	Enable additional hooks used by death, action and base-building events.
`detailedLogsNoPause`	Use 1 to keep logging when no players are online; 0 allows automatic pausing.
`detailedLogsApiPost`	Use 1 to enable HTTPS POST streaming, together with the event-specific detailedLogsApiPost options.
`detailedLogsPlayerPosition`	Position recording interval in seconds; 0 disables position recording.

Choose which events to record

Enable the categories needed for your investigations: player activity, combat, equipment, inventory, world events and server health. Expansion AI, trader and other Expansion categories require the corresponding mods to be installed.

A category that is disabled on the server supplies no events for DZLoggy to analyze. Begin with a supplied preset, then adjust the categories to suit your server and available log storage.

See what Detailed Logs can record

Session log files

Session files are written to $profile:DetailedLogs/dl_*.ljson. Each line contains a JSON event. A new server session creates a new file, which you can upload to DZLoggy.

If no events appear, check that logging is enabled, JSON output is selected, and a player has joined the server. Confirm that your launch command loads @detailedLogs with -serverMod.

Configure real-time streaming

Streaming uses a separate file: $profile:DetailedLogs/ApiConfig.json. Copy the configuration from your DZLoggy instance’s API setup; it contains that instance’s ingestion URL and API key.

Enable detailedLogsApiPost and the event-specific streaming switches you need, then restart the server. Keep the API key private. The public API examples use placeholders; your instance setup supplies the actual credentials after you sign in.