Start TrialStart Free TrialStart Free TrialBook Your DemoSign In

Juniper SRX Firewall

Ship your Juniper SRX firewall logs using Filebeat to your Stack

Configure a Juniper SRX firewall to ship logs via Filebeat to your stacks via Logstash.

Send Your DataLogsFirewallsJuniper SRX Firewall Guide

Follow this step by step guide to get 'logs' from your system to

Step 1 - Install Filebeat

To get started first follow the steps below:

  • Install
  • Root access
  • Verify the required port is open

Older versions can be found here 7, 6, 5

Step 2 - Configure Juniper SRX Logging

Configure the Juniper SRX firewall to log to a syslog server:

Ensure that your Juniper firewall is configured to send logs to your Filebeat server, meeting the required configuration criteria:

  • Log format: syslog
  • Send over: UDP
  • Port: 514

Step 3 - Configure Filebeat.yml

The configuration file below is pre-configured to send data to your Stack.

Copy the configuration file below and overwrite the contents of the Filebeat configuration file typically located at /etc/filebeat/filebeat.yml

# ============================== Filebeat inputs ===============================

- type: udp
  max_message_size: 10MiB
  host: ""
  enabled: true

  fields_under_root: true
  encoding: utf-8
  ignore_older: 12h

# ================================== Outputs ===================================
    hosts: ["your-logstash-host:your-ssl-port"]
    loadbalance: true
    ssl.enabled: true

If you’re running Filebeat 7, add this code block to the end. Otherwise, you can leave it out.

# ... For Filebeat 7 only ...
filebeat.registry.path: /var/lib/filebeat

If you’re running Filebeat 6, add this code block to the end.

# ... For Filebeat 6 only ...
registry_file: /var/lib/filebeat/registry

It’s a good idea to run the configuration file through a YAML validator to rule out indentation errors, clean up extra characters, and check if your YAML file is valid. is a great choice.

Step 4 - Validate configuration

If you have issues starting in the next step, you can use these commands below to troubleshoot.

Let's check the configuration file is syntactically correct by running directly inside the terminal. If the file is invalid, will print an error loading config file error message with details on how to correct the problem.


sudo  -e -c /etc//.yml


sudo ./ -e -c .yml


.\.exe -e -c .yml

Step 5 - Start filebeat

Start or restart to apply the configuration changes.

Step 6 - Launch to view your logs

Now you should view your data:

Launch Dashboard

If you don't see logs take a look at How to diagnose no data in Stack below for how to diagnose common issues.

Step 7 - How to diagnose no data in Stack

If you don't see data appearing in your Stack after following the steps, visit the Help Centre guide for steps to diagnose no data appearing in your Stack or Chat to support now.

Step 8 - Juniper SRX Overview

Enterprises can rely on Juniper SRX firewalls for advanced network security in protecting against cyber threats and unauthorized access. However, to effectively monitor and analyze network activity, a reliable and efficient log management solution is essential. Luckily, the Juniper SRX firewalls generate logs that capture valuable information about network traffic, threats, and user activity.

Organizations can effectively manage these logs by using Filebeat, an open-source shipping tool, to send logs from Juniper SRX firewalls to various destinations, including Elasticsearch, Logstash, and Kibana. Filebeat's reliability and minimal memory footprint make it a popular choice for sending logs to different destinations. It's also compatible and easy to use.

To send Juniper SRX firewall logs to Filebeat, organizations need to configure the firewall to forward logs to a syslog server, and then use Filebeat to collect and forward log data to Elasticsearch or other destinations. This involves setting up a syslog server to receive the logs, configuring the firewall to send logs to the syslog server, and configuring Filebeat to collect and forward the logs from the syslog server to Elasticsearch or other destinations.

Filebeat offers a filebeat.yml wizard to help users avoid complex logging concerns, such as large registry files and frequent errors encountered when handling deleted or renamed log files. Additionally, users can opt to use our Hosted ELK service to simplify tracking numerous pipelines using this shipper.

If you need any further assistance with migrating your log data to ELK we're here to help you get started. Feel free to get in contact with our support team by sending us a message via live chat & we'll be happy to assist.

Return to Search
Sign Up

© 2023 Ltd, All rights reserved.