Brewing in Beats: Shipped RC1

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.

Release 1.0.0-RC1

We released 1.0.0-RC1 this past week after closing a total of 100 pull requests in Github.  See the blog post for more details.

When using Logstash as output in your Beat, you need to make sure you have the latest Logstash Beats Input plugin installed by updating the plugin. Note that the current version of Logstash is not coming with the latest Logstash Beats Input plugin, so you need to update the Logstash Beats Input plugin after installing Logstash 2.0.0.

We are thrilled to see that so many people are trying out our software and help us improve it by posting issues on the Discuss Forum or Github. Lots of issues were fixed during this week. The most interesting ones are:

  • Filebeat was not reading existing files when they were modified. filebeat#199
  • Configuration issues that appear due to not having a default value for some configuration options: topbeat#96 filebeat#198

New Community Beat

This week another community Beat was created, called uwsgibeat, that is used for uWSGI monitoring. It is a lightweight agent that reads stats from uWSGI server periodically. uWSGI server must expose its stats via Stats Server.

Give it a try and let us know what you think about it. Thank you KS Chan for creating your second Beat!

Configurable Topbeat output

Thanks to another community contributor, you can now choose what type of data Topbeat is outputting. You can select if you want system wide statistics, per process statistics, file system statistics or all of them.

Export actual memory usage in Topbeat

This Topbeat enhancement is coming from the community and as it changes the exported fields, we merged it in the RC1 release to get feedback about it before the GA release.  Two fields are added to the exported fields: swap.actual_used_p and mem.actual_used_p to include the actual used memory and swap in percentage.

Add timestamp to Beat log events

The Beat is logging itself everything is processing or failing. To be more precise in when the data is logged, we added the timestamp, including milliseconds, to each Beat log event, in this GitHub issue.

  • 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?