Configuration tl;dr

Item Description
Files Sample configuration
Encryption certificate
Listener Port 5015. For help finding your region’s listener host, see Account region.
Default log locations JSON (recommended): /var/ossec/logs/alerts/alerts.json
Plain text: /var/ossec/logs/alerts/alerts.log

Guided configuration

Before you begin, you’ll need: Filebeat 7 or Filebeat 6, root access

Configure Wazuh for JSON logging

In the Wazuh configuration file (/var/ossec/etc/ossec.conf), find the <logging> tag, and set the <log_format> property to json.


Restart Wazuh.

sudo systemctl restart wazuh-manager
Download the certificate

For HTTPS shipping, download the public certificate to your certificate authority folder.

sudo wget -P /etc/pki/tls/certs/
Add Wazuh as an input

In the Filebeat configuration file (/etc/filebeat/filebeat.yml), add Wazuh to the filebeat.inputs section.

Replace <<SHIPPING-TOKEN>> with the token of the account you want to ship to.

# ...
- type: log

  - /var/ossec/logs/alerts/alerts.json

    logzio_codec: json

    # Your account token. You can find your token at
    token: <<SHIPPING-TOKEN>>
    type: wazuh
  fields_under_root: true
  encoding: utf-8
  ignore_older: 3h

If you’re running Filebeat 7, paste this code block. Otherwise, you can leave it out.

# ... For Filebeat 7 only ...
filebeat.registry.path: /var/lib/filebeat
- rename:
    - from: "agent"
      to: "filebeat_agent"
    ignore_missing: true
- rename:
    - from: "log.file.path"
      to: "source"
    ignore_missing: true

If you’re running Filebeat 6, paste this code block.

# ... For Filebeat 6 only ...
registry_file: /var/lib/filebeat/registry
Add as an output

If is not an output, add it now.

Replace <<LISTENER-HOST>> with your region’s listener host (for example, For more information on finding your account’s region, see Account region.

# ...
  hosts: ["<<LISTENER-HOST>>:5015"]
    certificate_authorities: ['/etc/pki/tls/certs/COMODORSADomainValidationSecureServerCA.crt']
Start Filebeat

Start or restart Filebeat for the changes to take effect.

Check for your logs

Give your logs some time to get from your system to ours, and then open Kibana.

If you still don’t see your logs, see log shipping troubleshooting.