Skip to content

Collect, process and visualise statistics from zeropingheroes/lancache with ELK

Notifications You must be signed in to change notification settings

zeropingheroes/lancache-elk

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

77 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

lancache-elk

Collect, process and visualise statistics from zeropingheroes/lancache with Elasticsearch, Logstash and Kibana

Screenshots

These screenshots are taken from a 100 person event, with the cache pre-loaded using zeropingheroes/lancache-autofill

Dashboard - General

Dashboard - General

Dashboard - Steam

Dashboard - General

Dashboard - Errors

Dashboard - General

Requirements

ELK Server

  • Ubuntu Server 18.04

Lancache Server

lancache-elk cannot be run on the same host as lancache as both use port 80.

Installation

  1. git clone https://github.com/zeropingheroes/lancache-elk.git && cd lancache-elk

  2. cp .env.example .env

  3. nano .env - add a password for the web interface

  4. ./install.sh

  5. Log into the Kibana web interface and go to Management > Saved Objects

  6. Import lancache-elk/configs/kibana/export.json choosing "logstash-*" in the dropdown under "New index pattern"

  7. Repeat step 6 a second time - not sure exactly why this is necessary...

Available Dashboards

  • Overall - Global cumulative data about the cache
  • General - Visualisations that apply to any upstream
  • Steam - See which depots are cached, and which Steam users are downloading games

Known Issues

Incorrect Cache Hit/Miss Stats for Blizzard and Origin

Because we use slice for these upstreams, Nginx reports a cache hit for almost all requests from clients, as the single client request has spawned one or more subrequests which fill the cache. This also means that our statistics for how much data has been added to the cache is incorrect too. If you have a workaround for this behaviour, please submit a pull request.

Troubleshooting

Check your ELK server's log files:

tail /var/log/logstash/logstash-plain.log
tail /var/log/elasticsearch/elasticsearch.log
journalctl -u kibana.service

Check your lancache server's log files:

tail /var/log/filebeat/filebeat
journalctl -u filebeat.service

Contributing

Please submit pull requests for improving the configuration files here.

For example:

  • Extracting additional fields from URIs
  • Useful Kibana visualisations

Useful sites:

About

Collect, process and visualise statistics from zeropingheroes/lancache with ELK

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages