Brewing in Beats: Redisbeat from community

Welcome to Weekly Beats! With this series, we're keeping you up to date with all that's new in Beats, from the details of work in progress pull requests to releases and learning resources.

Last week we continue working on the big features that will be available in the next major release: add support for flows in Packetbeat and generic filtering in libbeat. Beside these features, we are improving continuously the documentation based on our users feedback.

The highlights this week are:

New community Beat: Redisbeat

Redisbeat is used for Redis monitoring. It is a lightweight agent that periodically reads the status from the Redis INFO command. It exports general information about the Redis server, about the clients, memory statistics, persistence statistics, redis general statistics, replication statistics, CPU statistics, Redis commands statistics, cluster statistics and keyspace statistics.

Enhancements in Packetbeat

We are thrilled to receive two big pull requests this week from the community to add support for AMQP in Packetbeat and add support for extended PostgreSQL queries in Packetbeat. Big Thank you to the contributors and we will do our best to merge them as soon as possible.

Enhancements in Topbeat

Topbeat adds more information to the running processes. It now exports the username that started the process. This information might be useful in case the same command is started by different users and username seems to be the only way to differentiate between them in the Kibana dashboards. This enhancement is available on Unix and Windows systems and the implementation can be found here.

  • We're hiring

    Work for a global, distributed team where finding someone like you is just a Zoom meeting away. Flexible work with impact? Development opportunities from the start?