Collects and publishes Prometheus metrics from Battleye RCON and Steam A2S Query for DayZ server.

DayZ Prometheus Metrics Exporter is a powerful, cross-platform solution for collecting and publishing metrics from DayZ servers, supporting all major operating systems. It offers a ready-to-use Container image for easy deployment and provides full GeoIP support for player geolocation. The exporter collects data via Battleye RCON and Steam A2S Query, offering insights into server status, online players, bans, and more. Best of all, it requires no mods to be installed on the server. With fast setup, flexibility, and scalability, it's the perfect tool for monitoring DayZ servers in any environment.

• Configuration
• Metrics
• Endpoints
• Setup Exporter
  • Container Image
  • Systemd service
  • Windows service
• Collect metrics
• Visualize in Grafana
• Support me ☕

Grafana dashboard example

Usage:
  ./dayz-exporter [option] [config.yaml]

Available options:
  -y, --get-yaml    Prints an example YAML configuration file.
  -e, --get-env     Prints an example .env file.
  -v, --version     Show version, commit, and build time.
  -h, --help        Prints this help message.

Run the program with a custom configuration file:

./dayz-exporter config.yaml

Configuration File Lookup:

• The program first checks for a configuration file specified by the variable DAYZ_EXPORTER_CONFIG_PATH.
• If the config variable is not set, it will attempt to use a configuration file passed as a command-line argument.
• If no argument is provided, it will attempt to read from the default file config.yaml in the current directory.

You can get a sample YAML configuration here example.config.yaml, or save a sample YAML configuration to a file from within the application itself by running:

./dayz-exporter --get-yaml > config.yaml

You can get a sample of environment variables here example.env, or save to a file from within the application itself by running:

./dayz-exporter --get-env > dayz-exporter.env

YAML configuration options take priority over environment variables. If you use both, comment out the options in YAML that you wish to override using environment variables.

DAYZ_EXPORTER_RCON_PASSWORD=strong ./dayz-exporter config.yaml

For more information on configuration parameters, refer to the example configuration files (YAML and .env).

Metrics collected using the A2S INFO protocol provide information about players online, server status, etc., and a list of labels is generated.
Metrics collected by Battleye RCON provide detailed information about each player or entry in the ban list.

• a2s_info_players_online — Online players;
• a2s_info_players_slots — Players slots count;
• a2s_info_players_queue — Players wait in queue;
• a2s_info_time — Duration of day time on server;

• bercon_player_ping_seconds — Player ping in seconds. Extra labels: name, ip, guid, lobby, country ℹ️
• bercon_players_total — Total count of players;
• bercon_players_online — Count of players online;
• bercon_players_lobby — Count of players in lobby;
• bercon_players_invalid — Count of invalid players.

• bercon_ban_guid_time_seconds — Time left for GUID bans in seconds. Extra labels: reason, guid;
• bercon_ban_guid_total — Total count of GUID bans;
• bercon_ban_ip_time_seconds — Time left for IP bans in seconds. Extra labels: reason, ip, country ℹ️
• bercon_ban_ip_total — Total count of IP bans;

• server — Server name;
• map — Server map name;
• game — Game name;
• os — Server platform OS name;
• version — Game server version;
• Any static additional labels can also be installed via the application configuration.

The DayZ exporter exposes several useful endpoints for monitoring and troubleshooting:

• /: Provides an overview of the exporter and includes useful information about the status of the service, the connected game server, and the exporter version.
• /metrics: Exposes Prometheus-compatible metrics. This is the main endpoint used by Prometheus to scrape metrics from the exporter. It is typically accessed by your Prometheus instance for metric collection.
• /health: A general health check of the service. It provides an overall status of the exporter.
• /health/liveness: A liveness check endpoint that verifies if the service is alive. This checks the RCON connection to ensure the exporter is functioning.
• /health/readiness: A readiness check endpoint that ensures the service is fully operational, i.e., all required connections (like RCON and Steam) are established and functional.

Index page example on / route

The images are published to two container registries:

• docker pull ghcr.io/woozymasta/dayz-exporter:latest
• docker pull docker.io/woozymasta/dayz-exporter:latest

Quick start:

# Pull the image
docker pull ghcr.io/woozymasta/dayz-exporter:latest
# Generate an example YAML config
docker run --rm -ti ghcr.io/woozymasta/dayz-exporter:latest --get-yaml > dayz-exporter.yaml
# Edit the config file
editor dayz-exporter.yaml
# Run the container with the mounted config and exposed port
docker run --name dayz-exporter -d \
  -v "$PWD/dayz-exporter.yaml:/config.yaml" -p 8098:8098 \
  ghcr.io/woozymasta/dayz-exporter:latest

You can also use environment variables instead of a configuration file by running --get-env to get an example and passing them as container environment variables.

To run the DayZ exporter as a systemd service, use the following example configuration. This ensures the exporter runs on system startup.

[Unit]
Description=DayZ Prometheus Metrics Exporter
Documentation=https://woozymasta.github.io/dayz-exporter/
Wants=network-online.target
After=network-online.target dayz-server.target

[Service]
EnvironmentFile=-/etc/dayz-exporter.env
ExecStart=/usr/bin/dayz-exporter
Restart=on-failure
RestartSec=5s

[Install]
WantedBy=multi-user.target

Save this as /etc/systemd/system/dayz-exporter.service and enable it using

systemctl enable dayz-exporter
systemctl start dayz-exporter

You can also use a user-specific systemd service, for example, located in ~/.config/systemd/user/[email protected]. This allows you to manage multiple instances of the application simultaneously under the same user.

In this example, one service manages multiple server instances. Ensure that the %i argument is added symmetrically to the server launch parameters to map ports correctly.

[Unit]
Description=DayZ Prometheus Metrics Exporter 'Server %I'
Documentation=https://woozymasta.github.io/dayz-exporter/
Wants=network-online.target
After=network-online.target dayz-server@%i.target

[Service]
WorkingDirectory=%h/dayz/
EnvironmentFile=-%h/.dayz-exporter.env
Environment="DAYZ_EXPORTER_LISTEN_PORT=809%i"
Environment="DAYZ_EXPORTER_QUERY_PORT=2702%i"
Environment="DAYZ_EXPORTER_RCON_PORT=230%i5"
ExecStart=%h/.local/bin/dayz-exporter
Restart=on-failure
RestartSec=5s

[Install]
WantedBy=default.target

You can run the exporter using any method that suits you, but it's recommended to use a Windows service for better management and reliability.

To register the service, assuming the application and configuration are already downloaded and set up in the C:\dayz-exporter directory, use the following commands:

sc.exe create dayz-exporter `
  binPath= "C:\dayz-exporter\dayz-exporter.exe C:\dayz-exporter\config.yaml" `
  DisplayName= "DayZ metrics exporter" `
  start= auto

sc.exe start dayz-exporter
sc.exe query dayz-exporter

Open http://127.0.0.1:8098/ in your browser to check if the service is running properly.

sc.exe stop dayz-exporter
sc.exe query dayz-exporter
sc.exe delete dayz-exporter

Ensure that you have a running Prometheus instance to collect metrics from the DayZ exporter.

To configure Prometheus, add the following job to your prometheus.yml file:

scrape_configs:
  - job_name: dayz
    # scrape_interval: 1m
    static_configs:
      - targets:
        - '<DAYZ_EXPORTER_HOST>:8091'
        - '<DAYZ_EXPORTER_HOST>:8092'
        - '<DAYZ_EXPORTER_HOST>:8093'

Replace <DAYZ_EXPORTER_HOST> with the IP or hostname of your DayZ exporter instance.

If you wish to collect resource utilization metrics (e.g., CPU, memory) for your DayZ servers, and also populate the uptime panel in Grafana, you can use the optional process-exporter. This will collect and expose additional metrics to Prometheus.

Once the process exporter is installed and configured, it will collect and expose resource metrics to Prometheus. It will also provide additional data that will be displayed in the Grafana dashboard.

Example configuration for the process exporter to collect DayZ server process metrics:

process_names:
  - name: "dayz-{{.Matches.ConfigName}}-{{.Matches.Port}}"
    exe:
      - "DayZServer"
    cmdline:
      - '-config=(.*\/)?(?P<ConfigName>.*)\.cfg'
      - '-port=(.*\/)?(?P<Port>[0-9]+)'

Don't forget to also add metrics collection with process-exporter to scrape_configs in Prometheus.

To visualize the collected metrics, you'll need a running Grafana instance.

• Main Dashboard: Import the main dashboard from the file dayz-rcon.json or by ID 22457 from the Grafana dashboards.
  This dashboard will display key metrics, such as player counts and other relevant information.

• Optional: Process Exporter Dashboard: If you have set up the process exporter, import the additional dashboard from system-process.json or by ID 22458 from the Grafana dashboards.
  This dashboard provides insights into resource utilization (CPU, memory, etc.) for your DayZ servers.

If you enjoy my projects and want to support further development, feel free to donate! Every contribution helps to keep the work going. Thank you!

• BTC: 1Jb6vZAMVLQ9wwkyZfx2XgL5cjPfJ8UU3c
• USDT (TRC20): TN99xawQTZKraRyvPAwMT4UfoS57hdH8Kz
• TON: UQBB5D7cL5EW3rHM_44rur9RDMz_fvg222R4dFiCAzBO_ptH

Your support is greatly appreciated!