bunny.net CDN
Ship your bunny.net logs using Filebeat to your Logit.io Stack
Configure a bunny.net to ship logs via Filebeat to your Logit.io stacks via Logstash.
Install Integration
Install Filebeat
To get started you will need to install filebeat. To do this you have two main options:
- Choose the filebeat (opens in a new tab) ZIP file (Windows ZIP x86_64) or
- Choose the Microsoft Software Installer MSI (opens in a new tab) file (Windows MSI x86_64 (beta))
To successfully install filebeat and set up the required Windows service you will need to have administrator access.
If you have chosen to download the zip file:
- Extract the contents of the zip file into C:\Program Files.
- Rename the extracted folder to filebeat
- Open a PowerShell prompt as an Administrator (right-click the PowerShell icon and select Run As Administrator).
- From the PowerShell prompt, run the following commands to install filebeat as a Windows service:
cd 'C:\Program Files\filebeat'
.\install-service-filebeat.ps1
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-filebeat.ps1
For more information about Powershell execution policies see here (opens in a new tab).
If you have chosen to download the filebeat.msi file:
- double-click on it and the relevant files will be downloaded.
At the end of the installation process you'll be given the option to open the folder where filebeat has been installed.
- Open a PowerShell prompt as an Administrator (right-click the PowerShell icon and select Run As Administrator).
- From the PowerShell prompt, change directory to the location where filebeat was installed and run the following command to install filebeat as a Windows service:
.\install-service-filebeat.ps1
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-filebeat.ps1
For more information about Powershell execution policies see here (opens in a new tab).
Configure bunny.net Logging
Configure the bunny.net content delivery network to log to a syslog server:
To select logs from a Pull Zone on bunny.net, log in to your account and navigate to the details page of the Pull Zone
On the left side panel, click on "Security" and select "Logging", ensure that both "Enable logging" and "Enable log forwarding" switches are turned on
Under the "Syslog Endpoint" section enter the following:
- Hostname: FILEBEAT-IP-ADDRESS
- Port: 514
- Log Server Protocol: UDP
- Log Format: Plain Text
Save the Forwarding Configuration.
Configure Filebeat.yml
The configuration file below is pre-configured to send data to your Logit.io Stack.
Copy the configuration file below and overwrite the contents of the Filebeat
configuration file typically located at /etc/filebeat/filebeat.yml
####################### Logit.io Filebeat Configuration ########################
# ============================== Filebeat inputs ===============================
filebeat.inputs:
- type: udp
max_message_size: 10MiB
host: "0.0.0.0:514"
enabled: true
fields:
type: "bunny-net"
fields_under_root: true
encoding: utf-8
ignore_older: 12h
# ================================== Outputs ===================================
output.logstash:
hosts: ["@logstash.host:@logstash.sslPort"]
loadbalance: true
ssl.enabled: true
Validate configuration
.\@beatname.exe test config -c @beatname.yml
If the yml file is invalid, @beatname will print a description of the error. For example, if the
output.logstash
section was missing, @beatname would print no outputs are defined, please define one under the output section
Start Filebeat
To start Filebeat, run in Powershell:
Start-Service filebeat
Launch Logit.io to view your logs
Data should now have been sent to your Stack.
View My DataIf you don't see take a look at How to diagnose no data in Stack below for how to diagnose common issues.
How to diagnose no data in Stack
If you don't see data appearing in your stack after following this integration, take a look at the troubleshooting guide for steps to diagnose and resolve the problem or contact our support team and we'll be happy to assist.
bunny.net Overview
Bunny.net is a powerful content delivery network that provides fast and reliable content delivery for websites, videos, and other online content. To effectively monitor and analyze the performance of your Bunny.net CDN, it is essential to have a reliable and efficient log management solution. The Bunny.net CDN generates logs that capture information about network traffic, user activity, and content delivery.
To manage these logs effectively, organizations can use Filebeat, an open-source shipping tool, to send logs from the Bunny.net CDN to various destinations, including OpenSearch, Logstash, and Kibana, due to its reliability and minimal memory footprint. Filebeat is widely used to send logs from Bunny.net CDN to various destinations, including OpenSearch, Logstash, and Kibana, due to its compatibility and ease of use.
To send Bunny.net CDN logs to Filebeat, organizations can configure the CDN to forward logs to a syslog server, and then use Filebeat to collect and forward log data to OpenSearch or other destinations. This process involves setting up a syslog server to receive the logs, configuring the CDN to send logs to the syslog server, and configuring Filebeat to collect and forward the logs from the syslog server to OpenSearch or other destinations.
In summary, using Filebeat to send Bunny.net CDN logs to various destinations, including Elasticsearch, Logstash, and Kibana, is a reliable and efficient log management solution. By configuring the CDN to forward logs to a syslog server and using Filebeat to collect and forward the logs to Logit.io, organizations can gain insights into network traffic, user activity, and content delivery, and take action to improve the performance and reliability of their Bunny.net CDN.
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.