Guided configuration

You’ll need: Filebeat 7 or Filebeat 6, root access

  1. Configure FortiGate logging

    Configure your FortiGate firewall to send logs to your Filebeat server. Make sure you meet this configuration:

    • Log format: syslog
    • Send over: UDP
    • IP address: Filebeat server IP address
    • Port 514

    See the FortiGate docs for more information on configuring your FortiGate firewall.

    Sample commands for FortiOS 6.2

    config log syslogd setting
    set status enable
    set format default
    set server <FILEBEAT-SERVER-IP-ADDR>
    set port 514
  2. Download the certificate to your Filebeat server

    sudo wget -P /etc/pki/tls/certs/
  3. Add UDP traffic as an input

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

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

    # ...
    - type: udp
      max_message_size: 10MiB
      host: ""
        logzio_codec: plain
        # Your account token. You can find your token at
        token: <<SHIPPING-TOKEN>>
        type: fortigate
      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
  4. 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']
  5. Start Filebeat

    Start or restart Filebeat for the changes to take effect.

  6. 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.