# Ingest processor: Attaching header information to all the following log entries

**URL:** <https://discuss.elastic.co/t/ingest-processor-attaching-header-information-to-all-the-following-log-entries/193966>\
**Category:** Elasticsearch\
**Created:** [August 6, 2019, 9:03am UTC](https://discuss.elastic.co/t/ingest-processor-attaching-header-information-to-all-the-following-log-entries/193966 "2019-08-06T09:03:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![EldrosKandar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eldroskandar/32/33188_2.png) [@EldrosKandar](https://discuss.elastic.co/u/EldrosKandar)\
**Post date:** [August 6, 2019, 9:03am UTC](https://discuss.elastic.co/t/ingest-processor-attaching-header-information-to-all-the-following-log-entries/193966/1 "2019-08-06T09:03:43Z")

</div>

I'm using Filebeat and Ingest node to feed my ELK stack with logs. The first line of the log is an header with a different format but information relevant to the rest of the log entries. Is there a way to forward this information to the other parsed entries from the same source?

---

<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 3, 2019, 9:03am UTC](https://discuss.elastic.co/t/ingest-processor-attaching-header-information-to-all-the-following-log-entries/193966/2 "2019-09-03T09:03:53Z")

</div>

Closed on September 3, 2019, 9:03am UTC

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