Kids is a log aggregation system.

It aggregates messages like Scribe and its pub/sub pattern is ported from Redis.

• Real-time subscription
• Distributed collection
• Message persistence
• Multithreading
• Redis protocol
• No third-party dependencies

kids releases are available on the Github project releases page. Binaries are available for 64bit Linux, with package for Debian based distributions.

There is an example conf in Debian packages, but it is not useful in production, to deploy in production, see Run in production.

You need a complier with C++11 support like GCC 4.7 (or later) or Clang.

Download a source release, then:

tar xzf kids-VERSION.tar.gz
cd kids-VERSION
./configure
make
make test  # optional
make install

By default, it will be installed to /usr/local/bin/kids. You can use the --prefix option to specify the installation location. Run ./configure --help for more config options.

Kids comes with some sample config files in samples/, after building, simply run:

kids -c samples/dev.conf

Because kids uses redis protocol, you can use redis-cli to play with it, open another terminal:

$ redis-cli -p 3888
$ 127.0.0.1:3388> PSUBSCRIBE *

In yet another terminal:

$ redis-cli -p 3388
$ 127.0.0.1:3388> PUBLISH kids.testtopic message

redis-cli needs redis to be installed. On Mac, you can run brew install redis to install it. On Linux, run sudo apt-get install redis-tools

Run kids --help for more running options.

In production, we deploy kids agent at every host, which forwards log to a kids server, after deployment, you can use any redis client to publish log to local kids agent, and subscribe to kids server to consume the log.

To simplify deployment, use a package or a docker container.

If you do not have to include config in the package, this may happen, for example, you use puppet or saltstack to manage your configuration file, then you do not have to make the package yourself, just download it from kids's Github releases page.

See here.

Prerequisites:

• fpm

Download kids source release, then:

tar xzf kids-VERSION.tar.gz
cd kids-VERSION
cp samples/agent.conf debian/kids.conf
# EDIT kids.conf, minimally fill in server address
make deb

For server, use the same deb package and overwrite /etc/kids.conf with server's config file.

You can use docker to build a kids container to run or use it to make a deb package and run kids outside a container.

First do the following:

git clone https://github.com/zhihu/kids.git
cd kids
# or samples/server.conf
copy samples/agent.conf debian/kids.conf
# Edit kids.conf, minimally logfile should be set to stdout 
# to make `docker logs` work if you run kids in a container.

In the project root directory, run:

docker build -t zhihu/kids .

Now you can run it like so:

docker run -d -p 3388:3388 zhihu/kids

Make sure you have built the zhihu/kids image, because the zhihu/kids-deb depends on it.

cd debian
docker build -t zhihu/kid-deb .

You can now use the image to get a deb package.

docker run -v /path/to/save/deb:/deb zhihu/kids-deb

You will need

• build-essential
• libtool
• automake
• c++ compiler with c++ 11 support like gcc4.7+ or Clang

to build kids from source. Run the following to build kids:

./autogen.sh
./configure
make

Kids Uses BSD-3, see LICENSE for more details.

Q: What is the meaning of "kids"?
A: "kids" is the recursive acronym of "Kids Is Data Stream".

You can view the Chinese version README here