WildFly

The WildFly source collects logs from WildFly application servers by tailing their log files. It reads standalone server logs, and optionally domain server and domain controller logs, and parses the entries into structured records.

Supported Telemetry Types

Platform	Metrics	Logs	Traces
Linux		✓
Windows		✓

Prerequisites

WildFly must be writing its log files to disk, and the collector must run on a host where it can read those file paths (or the files must be shipped to that host). The configured paths must match where your WildFly installation actually writes logs.

By default WildFly writes the standalone server log to WILDFLY_HOME/standalone/log/server.log. In managed-domain mode, per-server logs are written under WILDFLY_HOME/domain/servers/*/log/server.log and host controller logs under WILDFLY_HOME/domain/log/. If your installation uses a non-default WILDFLY_HOME or a customized logging subsystem, adjust the file paths accordingly.

For details on WildFly logging, the logging subsystem, and log file locations, see the official WildFly Admin Guide: Logging Configuration.

Configuration

Logs

Parameter	Type	Required	Default	Description
Standalone Server File Path(s)	Strings	No	/opt/wildfly/standalone/log/server.log	File paths to tail for standalone server logs.
Domain Server Logs	Boolean	No	true	Enable to read domain server logs.
Domain Server File Path(s)	Strings	No	/opt/wildfly/domain/servers/*/log/server.log	File paths to tail for domain server logs. Shown when Domain Server Logs is enabled.
Domain Controller Logs	Boolean	No	true	Enable to read domain controller logs.
Domain Controller File Path(s)	Strings	No	/opt/wildfly/domain/log/*.log	File paths to tail for domain controller logs. Shown when Domain Controller Logs is enabled.

Advanced

Parameter	Type	Required	Default	Description
Start At	Enum: beginning, end	No	end	Start reading logs from the beginning or end of the file.
Timezone	Timezone	No	UTC	The timezone to use when parsing timestamps.
Parse	Boolean	No	true	Parses the log fields into structured data.

Examples

Standalone server only

Collect logs from a single standalone WildFly server installed at the default location, disabling the domain log readers.

- name: standalone_file_path
  value:
    - /opt/wildfly/standalone/log/server.log
- name: enable_domain_server
  value: false
- name: enable_domain_controller
  value: false

Configuration Tips

• The default paths assume WILDFLY_HOME is /opt/wildfly. If you installed WildFly elsewhere, update each file path to match your installation.
• Leave Parse enabled to extract structured fields from each log line. Disable it only if your log format is customized and the parser cannot read it, in which case the raw line is preserved.
• Set Start At to beginning to backfill existing log content on first run, or leave it at end to collect only new entries.

Troubleshooting

Symptom: No logs are collected. Solution: Confirm the configured file paths point to real files that WildFly is actively writing to. Verify the collector process has read permission on those paths and on their parent directories.

Symptom: Domain logs are missing even though domain mode is in use. Solution: Ensure Domain Server Logs and/or Domain Controller Logs are enabled, and that the glob paths match your domain layout (server names under domain/servers/*/log/).

Symptom: Timestamps are off by several hours. Solution: Set Timezone to the timezone WildFly uses when writing log timestamps, rather than leaving it at the default UTC.

Standalone Source

apiVersion: bindplane.observiq.com/v1
kind: Source
metadata:
  name: wildfly
spec:
  type: wildfly
  parameters:
    - name: standalone_file_path
      value:
        - /opt/wildfly/standalone/log/server.log
    - name: enable_domain_server
      value: true
    - name: domain_server_path
      value:
        - /opt/wildfly/domain/servers/*/log/server.log
    - name: enable_domain_controller
      value: true
    - name: domain_controller_path
      value:
        - /opt/wildfly/domain/log/*.log
    - name: start_at
      value: end
    - name: timezone
      value: UTC
    - name: parse
      value: true

Related Resources

• WildFly Admin Guide: Logging Configuration
• OpenTelemetry Filelog Receiver