# Workaround: Import and export pipelines, connections, rules

**URL:** <https://community.graylog.org/t/workaround-import-and-export-pipelines-connections-rules/967>\
**Category:** Graylog Central (peer support)\
**Tags:** pipeline-rules\
**Created:** [April 27, 2017, 3:44pm UTC](https://community.graylog.org/t/workaround-import-and-export-pipelines-connections-rules/967 "2017-04-27T15:44:05Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![ralberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/ralberto/32/938_2.png) [@ralberto](https://community.graylog.org/u/ralberto)\
**Post date:** [April 27, 2017, 3:44pm UTC](https://community.graylog.org/t/workaround-import-and-export-pipelines-connections-rules/967/1 "2017-04-27T15:44:05Z")

</div>

Hi all.

Import or export pipelines, rules, etc… [is currently not supported](https://github.com/Graylog2/graylog-plugin-pipeline-processor/issues/109), using the content pack approach. Export mongodb pipeline\_\* collections seems a fragile approach, but I don’t see any other options. Do you have any recommendation how to automate the installation process of a pre-configured graylog instance?

---

<div class="post-metadata">

**Author:** ![GTownson](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/gtownson/32/793_2.png) [@GTownson](https://community.graylog.org/u/GTownson)\
**Post date:** [July 12, 2018, 9:00am UTC](https://community.graylog.org/t/workaround-import-and-export-pipelines-connections-rules/967/2 "2018-07-12T09:00:50Z")

</div>

I think it’s crazy that pipelines cannot be exported within contents packs! Currently the only way other than manually is with the Mongodb export. Hopefully the funcitonality will be included into Graylog soon.

---

<div class="post-metadata">

**Author:** ![jochen](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jochen/32/8_2.png) [@jochen](https://community.graylog.org/u/jochen)\
**Post date:** [July 12, 2018, 9:03am UTC](https://community.graylog.org/t/workaround-import-and-export-pipelines-connections-rules/967/3 "2018-07-12T09:03:27Z")

</div>

> [@GTownson](#):
>
> Hopefully the funcitonality will be included into Graylog soon.

Secret hidden surprise GitHub issue which absolutely cannot be found via search or by opening the Graylog 3.0.0 milestone. 😉

> <https://github.com/Graylog2/graylog2-server/issues/2507>
>
> Processing Pipeline settings cannot be included in Content Packs but it would de…finitely make sense to share them easily.

---

<div class="post-metadata">

**Author:** ![GTownson](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/gtownson/32/793_2.png) [@GTownson](https://community.graylog.org/u/GTownson)\
**Post date:** [July 12, 2018, 9:06am UTC](https://community.graylog.org/t/workaround-import-and-export-pipelines-connections-rules/967/4 "2018-07-12T09:06:20Z")

</div>

What is this magical ‘GitHub’ you speak of? On a serious note, is there a rough due date for 3.0.0? I can see the progress bar and I presume you just need to complete all of the tasks on there and then you’ll be ready to reslease.

---

<div class="post-metadata">

**Author:** ![jochen](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jochen/32/8_2.png) [@jochen](https://community.graylog.org/u/jochen)\
**Post date:** [July 12, 2018, 9:07am UTC](https://community.graylog.org/t/workaround-import-and-export-pipelines-connections-rules/967/5 "2018-07-12T09:07:29Z")

</div>

> [@GTownson](#):
>
> is there a rough due date for 3.0.0?

Some time in Q3 2018, I guess.

---

<div class="post-metadata">

**Author:** ![GTownson](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/gtownson/32/793_2.png) [@GTownson](https://community.graylog.org/u/GTownson)\
**Post date:** [July 12, 2018, 9:08am UTC](https://community.graylog.org/t/workaround-import-and-export-pipelines-connections-rules/967/6 "2018-07-12T09:08:06Z")

</div>

Cheers for that. Can’t wait for it!!