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.
Follow this step by step guide to get 'logs' from your system to Logit.io:
Step 2 - 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.
Step 3 - 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
# ============================== Filebeat inputs ===============================
filebeat.inputs:
- type: udp
max_message_size: 10MiB
host: "0.0.0.0:514"
enabled: true
fields:
type:
fields_under_root: true
encoding: utf-8
ignore_older: 12h
# ================================== Outputs ===================================
output.logstash:
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. Yamllint.com 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.
deb/rpm
sudo -e -c /etc//.yml
macOS
cd <EXTRACTED_ARCHIVE>
sudo ./ -e -c .yml
Windows
cd <EXTRACTED_ARCHIVE>
.\.exe -e -c .yml
Step 5 - Start filebeat
Start or restart to apply the configuration changes.
Step 6 - Launch Logit.io to view your logs
Now you should view your data:
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 - 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.