# Collecting =\> parsing ansible outputs into elasticsearch

**URL:** <https://discuss.elastic.co/t/collecting-parsing-ansible-outputs-into-elasticsearch/156622>\
**Category:** Logstash\
**Created:** [November 14, 2018, 9:47am UTC](https://discuss.elastic.co/t/collecting-parsing-ansible-outputs-into-elasticsearch/156622 "2018-11-14T09:47:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![smm](https://avatars.discourse-cdn.com/v4/letter/s/bb73d2/32.png) [@smm](https://discuss.elastic.co/u/smm)\
**Post date:** [November 14, 2018, 9:47am UTC](https://discuss.elastic.co/t/collecting-parsing-ansible-outputs-into-elasticsearch/156622/1 "2018-11-14T09:47:06Z")

</div>

Dear community,  
my colleague collects ansible outputs (in case of errors) 1:1 into elasticsearch.  
Does someone have / share some valid parsing config for logstash for this kind of source so that the results in Kibana get more search and read friendly?  
Or: How would you do it?  
Thank you.

---

<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:** [December 12, 2018, 9:47am UTC](https://discuss.elastic.co/t/collecting-parsing-ansible-outputs-into-elasticsearch/156622/2 "2018-12-12T09:47:07Z")

</div>

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