This integration allows you to send logs from your network devices to your Logz.io account.
Before you begin, you'll need:
- Filebeat installed
- Root access
Configure your device
Configure your network device to send logs to your Filebeat server, TCP port 9000. See your device's documentation if you're not sure how to do this.
Download the Logz.io public certificate to your credentials server
For HTTPS shipping, download the Logz.io public certificate to your certificate authority folder.
sudo curl https://raw.githubusercontent.com/logzio/public-certificates/master/AAACertificateServices.crt --create-dirs -o /etc/pki/tls/certs/COMODORSADomainValidationSecureServerCA.crt
Add TCP traffic as an input
In the Filebeat configuration file (/etc/filebeat/filebeat.yml), add TCP to the filebeat.inputs section.
<<LOG-SHIPPING-TOKEN>> with the token of the account you want to ship to.
Filebeat requires a file extension specified for the log input.
- type: tcp
# You can manage your tokens at
Set Logz.io as the output
If Logz.io is not an output, add it now. Remove all other outputs.
<<LISTENER-HOST>> with the host for your region. For example,
listener.logz.io if your account is hosted on AWS US East, or
listener-nl.logz.io if hosted on Azure West Europe. The required port depends whether HTTP or HTTPS is used: HTTP = 8070, HTTPS = 8071.
Start or restart Filebeat for the changes to take effect.
Check Logz.io for your logs
Give your logs some time to get from your system to ours, and then open Open Search Dashboards.
If you still don't see your logs, see Filebeat troubleshooting.