dzo_logz

dzo_logz - Structured Logging for DayZ

A fork of LogZ by WoozyMasta, renamed to integrate more closely into dzo - the DayZ Server Operator. Servermod only. Can be installed alongside the original LogZ.

Where to install: server only. Do not install on clients - it does nothing on the client.

[hr][/hr]

What it is

A structured logging mod for DayZ servers that writes events in NDJSON (Newline Delimited JSON) format. Unlike standard textual .ADM or .RPT logs which are hard to parse, LogZ produces machine-readable logs rich in context (coordinates, HP, SteamIDs, inventory state, damage types). Designed to be ingested by ELK Stack (Elasticsearch, Logstash, Kibana), Loki, Graylog, or VictoriaLogs.

It focuses on server analytics and player behavior statistics rather than just error reporting. Ideal for building detailed dashboards to track player activity, combat, and economy.

Does not change gameplay and adds no items or loot.

[hr][/hr]

What dzo_logz adds

The fork keeps adding context and events so that what happened on a server can be reconstructed from the log alone - plain facts, no verdicts; what to make of them is up to your dashboards and tools.

• Combat context: every shot (with rounds left), every melee swing (hit or miss), hit zone, damage detail and the line of sight between attacker and hit point
• Periodic player (movement, stamina, vitals) and vehicle snapshots
• Session details: engine kick reason, login position flag, players who log out restrained or unconscious
• Server-side oddities: inventory juncture timeouts, hit claims, gas zone creation and its creator
• Optional DayZ Expansion events: code locks, base building and territories, teleports

[hr][/hr]

Who it’s for

• Server owners who want to visualize player activity and combat in Grafana or Kibana
• Admins needing detailed, searchable evidence for investigations (cheaters, abuse)
• DevOps enthusiasts building a professional monitoring stack

[hr][/hr]

Key points

• Server-only - players don’t need the mod
• Structured Data - every line is a valid JSON object
• Rich Context - logs include positions, distance, specific body part hit, ammo type, and hierarchy
• Performance - optimized serialization, damage thresholds, and event throttling (e.g., rapid fire)
• Log Rotation - built-in file rotation to prevent disk overflow
• Integrations - native support for MetricZ and DayZ-Expansion-AI

[hr][/hr]

Quick install

[olist] [*]Add the mod to your DayZ server load order: [code]-servermod=@dzo_logz[/code] [*]Start the server - log file appears at: [code].../profiles/logz.ndjson[/code] [*]Configure your log collector (Promtail, Filebeat, Vector) to tail this file [/olist]

[hr][/hr]

Log Collectors Configuration

When setting up Promtail, Fluent Bit, or Vector, ensure you parse the JSON line. We recommend using the following root fields as Labels (Tags) for efficient filtering:

• instance (Server ID)
• world (Map Name)
• level (Severity)
• event_type (e.g. "player.kill", "chat")

Important: Use the ts field (Unix epoch seconds) as the timestamp source to keep logs accurate even if the collector lags.

[hr][/hr]

Complete your stack with MetricZ

To get the full picture, use MetricZ alongside LogZ.

• LogZ tracks logs (Detailed events, combat history, economy flows)
• MetricZ tracks metrics (Server FPS, total entity counts, vehicle numbers)

Together they allow you to visualize not just what happened, but how it impacted server performance (e.g., did that massive explosion drop the FPS?).

[hr][/hr]

Source & docs

GitHub: bzed/dzo-logz (fork of WoozyMasta/logz)