Server Log Analysis
Reference for using server logs to inspect player activity, Central Economy loops, loot events, and operational issues.
Overview
Server logs are the closest thing to a black box recorder for a DayZ server. They show player actions, admin events, Central Economy loops, loot cleanup, dynamic events, and crash clues.
DZconfig log analysis turns uploaded ADM, RPT, LOG, TXT, JSON, or LJSON files into searchable operational data.
Quick Facts
| Useful files | ADM logs, RPT logs, server logs, and structured JSON/LJSON logs |
|---|---|
| Best for | Player investigation, economy review, event monitoring, and restart troubleshooting |
| Pair with | types.xml, events.xml, cfgeventspawns.xml, and serverDZ.cfg logging flags |
What to Look For
Player Activity
Movement, combat, deaths, connections, disconnections, and suspicious behavior.
CE Loops
Economy loop timing and count snapshots that reveal overpopulation or cleanup issues.
Dynamic Events
Spawned events, event types, positions, and timing across a restart window.
Loot Events
Item add/remove/cleanup traces that explain why loot may feel scarce or overloaded.
Operational Checks
If players report no loot, compare CE loops with types.xml changes and restart timing. The economy often needs multiple cycles before a change feels visible in-game.
If an event never appears, check the event definition, matching cfgeventspawns group, and whether the log shows errors for missing classnames or bad positions.
Logging Setup
| Flag or file | Purpose |
|---|---|
| -adminlog | Enables admin/player activity logging for investigation. |
| -dologs | Enables script and RPT-style logging useful for troubleshooting. |
| -netlog | Adds network detail, useful only when debugging connection problems. |
| serverDZ.cfg | Controls server identity, mission, and several gameplay-facing options. |