# Beats via Logstash and Elasticsearch

**URL:** <https://discuss.elastic.co/t/beats-via-logstash-and-elasticsearch/142460>\
**Category:** Beats\
**Created:** [August 1, 2018, 4:09am UTC](https://discuss.elastic.co/t/beats-via-logstash-and-elasticsearch/142460 "2018-08-01T04:09:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sanjeev\_Gopal](https://avatars.discourse-cdn.com/v4/letter/s/898d66/32.png) [@Sanjeev\_Gopal](https://discuss.elastic.co/u/Sanjeev_Gopal)\
**Post date:** [August 1, 2018, 4:09am UTC](https://discuss.elastic.co/t/beats-via-logstash-and-elasticsearch/142460/1 "2018-08-01T04:09:27Z")

</div>

Reference: [Conflicted about Beats, Logstash and ES](https://discuss.elastic.co/t/conflicted-about-beats-logstash-and-es/55427)

Lets say I pipe a few Beats (in a remote DC) through Logstash, and a few beats direct to ES, can I send them to the same index? Wondering if Logstash would change the events significantly, that I have to use different indexes.

I would also like to use the canned dashboards... hopefully as they are.

---

<div class="post-metadata">

**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\
**Post date:** [August 1, 2018, 3:33pm UTC](https://discuss.elastic.co/t/beats-via-logstash-and-elasticsearch/142460/2 "2018-08-01T15:33:01Z")

</div>

If you simply route the events through Logstash and follow the recommendations in our documentation for [installing the index template](https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-template.html#load-template-manually) and [naming your indices](https://www.elastic.co/guide/en/elastic-stack-overview/6.3/get-started-elastic-stack.html#logstash-setup) then things should work fine.

If you do any processing inside of Logstash just be mindful not to change the data types of existing fields and I think you'll be fine.

---

<div class="post-metadata">

**Author:** ![Sanjeev\_Gopal](https://avatars.discourse-cdn.com/v4/letter/s/898d66/32.png) [@Sanjeev\_Gopal](https://discuss.elastic.co/u/Sanjeev_Gopal)\
**Post date:** [August 8, 2018, 7:07am UTC](https://discuss.elastic.co/t/beats-via-logstash-and-elasticsearch/142460/3 "2018-08-08T07:07:56Z")

</div>

Thanks @andrewkroh! Almost there... but for these 2 issues:

- Few fields, like beat.name show up in Kibana as beat.name.keyword.
- Ended up with more than 1000 fields for Winlogbeat.

I fixed for both by updating the visualization and changing the template. But I'd like to understand what I could have done wrong. I'm not doing any filtering - just in/out.

What I'm actually doing is: Beats --\> Logstash --\> Logstash --\> Elasticsearch

---

<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:** [September 5, 2018, 9:08am UTC](https://discuss.elastic.co/t/beats-via-logstash-and-elasticsearch/142460/4 "2018-09-05T09:08:02Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.