# \[ANNOUNCEMENT\] Execbeat 3.2.0 released

**URL:** <https://discuss.elastic.co/t/announcement-execbeat-3-2-0-released/88278>\
**Category:** Community Ecosystem\
**Created:** [June 5, 2017, 1:59pm UTC](https://discuss.elastic.co/t/announcement-execbeat-3-2-0-released/88278 "2017-06-05T13:59:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![christiangalsterer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christiangalsterer/32/6447_2.png) [@christiangalsterer](https://discuss.elastic.co/u/christiangalsterer)\
**Post date:** [June 5, 2017, 1:59pm UTC](https://discuss.elastic.co/t/announcement-execbeat-3-2-0-released/88278/1 "2017-06-05T13:59:44Z")

</div>

I'm happy to announce the availability of [Execbeat 3.2.0]([https://github.com/christiangalsterer/execbeat/releases/tag/3.2,0](https://github.com/christiangalsterer/execbeat/releases/tag/3.2,0).

[Execbeat](https://github.com/christiangalsterer/execbeat) is a [Beat](https://www.elastic.co/products/beats) which executes (shell) commands in a regular interval and sends the standard output and standard error as an event to a configured shipper, e.g. elasticsearch and logstash.

Release 3.2.0 contains the following changes:

- [Use exit code 127 when command to execute is not found](https://github.com/christiangalsterer/execbeat/issues/15)

More information can be found on [github](https://github.com/christiangalsterer/execbeat).  
For ideas, bug reports etc please create an issue on the github project page or even better create a pull request.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 1:50pm UTC](https://discuss.elastic.co/t/announcement-execbeat-3-2-0-released/88278/2 "2017-07-06T13:50:48Z")

</div>