# Pipeline in pipe output Logstash

**URL:** https://discuss.elastic.co/t/pipeline-in-pipe-output-logstash/295032
**Category:** Logstash
**Created:** [January 21, 2022, 8:41am UTC](https://discuss.elastic.co/t/pipeline-in-pipe-output-logstash/295032 "2022-01-21T08:41:16Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![rodri.gz](https://avatars.discourse-cdn.com/v4/letter/r/aca169/32.png) [@rodri.gz](https://discuss.elastic.co/u/rodri.gz)
#### Post date: [January 21, 2022, 8:41am UTC](https://discuss.elastic.co/t/pipeline-in-pipe-output-logstash/295032/1 "2022-01-21T08:41:16Z")

</div>

hello!

I would like to know if, like an Elasticsearch output, we can use pipeline =\> "%{[@metadata][pipeline]}" for parsing logs, we could use these predefined pipelines in the pipe type output to parse previously parsed fields through the ingest pipeline

something like..

```auto
output {
  pipe {
    id => "my_plugin_id"
    pipeline => "name-of-the-module-pipeline
  }
}
 ---------- other pipeline ----------
input {
  pipe {
    id => "my_plugin_id"
  }
}

filter{
  grok ...

}

output {
      elasticsearch {
        host => xxxxx:9200
        index => "%{[some_field][sub_field]}-%{+YYYY.MM.dd}"
      }
    }

```

thank you in advanced!

---

<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: [February 18, 2022, 8:41am UTC](https://discuss.elastic.co/t/pipeline-in-pipe-output-logstash/295032/2 "2022-02-18T08:41:45Z")

</div>

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