Start your 14-day free trial today

No Credit Card Required

Try Free

Already have an account? Sign In

Send data via Cisco ASA Router to your Logstash instance provided by

Cisco ASA Router configuration

A log shipper designed for files.

Configure Filebeat to ship Cisco logs to Logstash and Elasticsearch.

Step 1 - Configure Cisco RouterCopy

Enable your Cisco ASA router to send logs to a remote server over TCP. As this isn't enabled by default you will need to enable it, you can follow the instructions here to do so.

Cisco Logs Instructions

Step 2 - Install FilebeatCopy

deb (Debian/Ubuntu/Mint)

curl -L -O
sudo dpkg -i -oss-7.15.1-amd64.deb

rpm (CentOS/RHEL/Fedora)

curl -L -O
sudo rpm -vi -oss-7.15.1-x86_64.rpm


curl -L -O
tar xzvf -oss-7.15.1-darwin-x86_64.tar.gz


  • Download and extract the Windows zip file.
  • Rename the -<version>-windows directory to ``.
  • Open a PowerShell prompt as an Administrator.
  • Run the following to install as a Windows service:
If script execution is disabled on your system, you need to set the execution policy for the current session to allow the script to run. For example: PowerShell.exe -ExecutionPolicy UnRestricted -File .\install-service-.ps1.
My OS isn't here! Chat to support now

Step 3 - Locate the configuration fileCopy

deb/rpm /etc/filebeat/filebeat.yml
mac/win <EXTRACTED_ARCHIVE>/filebeat.yml

Step 4 - Configure the inputsCopy

Now in the filebeat.inputs section of the config file. You need to enabe tcp input.

The host is the Filebeat server itself and the port is what you have chosen as the tcp port.

You can then apply additional configuration settings to add an extra field type to all logs that come through this input. This will help us indentify them easily in Elasticsearch/Kibana.


# Each - is an input. Most options can be set at the input level, so
# you can use different inputs for various configurations.
# Below are the input specific configurations.

- type: tcp
  host: ""
    type: cisco-asa

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

Step 5 - Enable the inputCopy

We need to ensure that any inputs we are using are enabled


- type: log
  enabled: false

Enable the filebeat input, so it should look like the following


- type: log
  enabled: true

Step 6 - Configure outputCopy

We'll be shipping to Logstash so that we have the option to run filters before the data is indexed.
Comment out the elasticsearch output block.

## Comment out elasticsearch output
#  hosts: ["localhost:9200"]
No input available! Your stack is missing the required input for this data source Talk to support to add the input

Step 7 - Validate configurationCopy

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


./ -e -c .yml


.\.exe -e -c .yml

Step 8 - Start filebeatCopy

Ok, time to start ingesting data!


sudo systemctl enable filebeat
sudo systemctl start filebeat




Start-Service filebeat

Step 9 - how to diagnose no data in StackCopy

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.

Toggle View

Expand View

Return to Search

© 2022 Ltd, All rights reserved.