Skip to content
High performance data aggregating storage
Go Shell
Branch: master
Clone or download
Latest commit 6998deb Oct 17, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
api allow to provide custom fields in Write operation Jul 11, 2019
build update build Jun 26, 2019
client allow to provide custom fields in Write operation Jul 11, 2019
cmd deleted collect.json for testing logfmt Aug 14, 2019
doc readme Mar 28, 2019
examples add api examples Jun 4, 2019
pkg changed visibility for map Aug 19, 2019
server time index first version May 16, 2019
.gitignore ignore binaries Apr 12, 2019
.travis.yml use go mod Apr 26, 2019
LICENSE very draft lr CLI Mar 1, 2019
Makefile Add Makefile Nov 14, 2018 Fixed typo Aug 6, 2019
go.mod use new log4g Oct 16, 2019
go.sum use new log4g Oct 16, 2019
install readme and install changes Apr 23, 2019
version.go releasing version v0.1.44 Sep 29, 2019

Go Report Card Build Status GoDocLicense

Logrange - streaming database

Logrange is highly performant streaming database for aggregating streams of records like application logs, system metrics, audit logs etc. from thousands of sources. Logrange provides an API to do operations from simple search to the data analysis and machine learning.

The product

  • Size tolerant. Logrange is able to store as much data as written there. The only limitation is the storage space available for the database.
  • Highly performant. Writing and reading millions of records per second (hundered megabytes or gigabytes of data).
  • Write optimized. Logrange persists the raw data in realtime. All other data processing like indexing can be done later.
  • Low latency. Data becomes available for read within milliseconds after it is written
  • Scalable. Supporting tens of thousands different streams of records (terrabytes of the data)
  • Highly available. In clustering solution, data could be replicated between logrange nodes. Logrange will support data and load distribution policies.
  • Native for stream processing. Merging, filtering and search using LQL (Logrange Query Language)
  • Open Source. Logrange is 100% open source. It can be used for building trustworthy data storages.
  • Ready to use. Basic installation includes pre-configured log processing tools: collector, forwarder, CLI tool and Logrange database service.
  • Easy installation either in a containerized (k8s or docker) or a custom environment.

Quick start

Logrange shipment includes 2 executables - logrange server and lr - the logrange client. In the quick start you can use precompiled binaries to try logrange out within 1 minute:

Step 1. Let's put everything into one dir

Make a directory and enter there:

mkdir lrquick
cd lrquick

Step 2. Install logrange server and run it

curl -s | bash -s logrange -d ./bin
./bin/logrange start --base-dir=./data --daemon

Normally, you have to see something like Started. pid=12345

Step 3. Install logrange client and start collecting logs from the machine

curl -s | bash -s lr -d ./bin
./bin/lr collect --storage-dir=./collector --daemon

The command above runs collector in background. It will send logs found in /var/log folder to the logrange server started in step 2.

Step 4. Connect to the server, using CLI tool.

./bin/lr shell

In the logrange shell, you can try select to retrieve collected data:

> select limit 10

Or try help command to find out what commands are available.

Quick stop

From the logrange folder (lrquick) type the following commands to stop collector and the logrange server:

./bin/lr stop-collect --storage-dir=./collector
./bin/logrange stop --base-dir=./data

Now, to clean up, just remove the lrquick folder:

cd ..
rm -rf ./lrquick/


k8s Installation
The product

Getting Help

  • Found a bug or thinking about a new feature? File an issue
  • If you have any question or feedback regarding Logrange, send us e-mail to:

Contact us

Whether you have problems with log aggregating, processing or analysis, or wanting to build a secure data aggregating solution.

Reach out to

Join our gitter chat


Apache License 2.0, see LICENSE.

You can’t perform that action at this time.