# "target\_prefix" equivalent for ingest pipeline?

**URL:** <https://discuss.elastic.co/t/target-prefix-equivalent-for-ingest-pipeline/337009>\
**Category:** Elasticsearch\
**Created:** [June 27, 2023, 3:06pm UTC](https://discuss.elastic.co/t/target-prefix-equivalent-for-ingest-pipeline/337009 "2023-06-27T15:06:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![andrew.klaassen](https://avatars.discourse-cdn.com/v4/letter/a/6f9a4e/32.png) [@andrew.klaassen](https://discuss.elastic.co/u/andrew.klaassen)\
**Post date:** [June 27, 2023, 3:06pm UTC](https://discuss.elastic.co/t/target-prefix-equivalent-for-ingest-pipeline/337009/1 "2023-06-27T15:06:25Z")

</div>

The filebeat dissect processor has a handy "target\_prefix" option, which allows everything it extracts to be placed under a common prefix.

Is there any equivalent for the dissect or grok processors in an ingest pipeline, or an easy way to accomplish the same thing for a grok pattern that's made up of a bunch of pattern definitions?

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [June 27, 2023, 3:21pm UTC](https://discuss.elastic.co/t/target-prefix-equivalent-for-ingest-pipeline/337009/2 "2023-06-27T15:21:55Z")

</div>

> [@andrew.klaassen](#):
>
> Is there any equivalent for the dissect or grok processors in an ingest pipeline, or an easy way to accomplish the same thing for a grok pattern that's made up of a bunch of pattern definitions?

I don't think so, there is nothing in the documentation for the `dissect` and `grok` processors.

The `dissect` and `grok` processors on an Ingest pipeline works similar to the same filters on a Logstash pipeline, where also there is no target\_prefix to store the fields on a top-level field.

If you need to store it on a top-level field as a prefix you will need to directly add the prefix on the fields names, for example, instead of `fieldName` you will need to use `prefix.fieldName`.

---

<div class="post-metadata">

**Author:** ![andrew.klaassen](https://avatars.discourse-cdn.com/v4/letter/a/6f9a4e/32.png) [@andrew.klaassen](https://discuss.elastic.co/u/andrew.klaassen)\
**Post date:** [June 27, 2023, 3:28pm UTC](https://discuss.elastic.co/t/target-prefix-equivalent-for-ingest-pipeline/337009/3 "2023-06-27T15:28:19Z")

</div>

Thanks.

---

<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 25, 2023, 3:29pm UTC](https://discuss.elastic.co/t/target-prefix-equivalent-for-ingest-pipeline/337009/4 "2023-07-25T15:29:08Z")

</div>

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