# Nginx and Mysql fields directly to Elasticsearch without Logstash

**URL:** https://discuss.elastic.co/t/nginx-and-mysql-fields-directly-to-elasticsearch-without-logstash/70148
**Category:** Beats
**Tags:** filebeat
**Created:** [December 28, 2016, 3:05pm UTC](https://discuss.elastic.co/t/nginx-and-mysql-fields-directly-to-elasticsearch-without-logstash/70148 "2016-12-28T15:05:13Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)
#### Post date: [December 29, 2016, 12:30am UTC](https://discuss.elastic.co/t/nginx-and-mysql-fields-directly-to-elasticsearch-without-logstash/70148/2 "2016-12-29T00:30:13Z")

</div>

The documentation you're looking at is build from the current development branch. What you're looking at is currently more of a prototype for a new feature coming to filebeat.

Also have a look [here](https://discuss.elastic.co/t/question-about-creating-brobeat/70025) and [here](https://github.com/elastic/beats/pull/3158).

---

_[View the full topic](https://discuss.elastic.co/t/nginx-and-mysql-fields-directly-to-elasticsearch-without-logstash/70148)._