# Newly added pipeline does not appear under monitoring **URL:** \ **Category:** Kibana\ **Created:** [February 23, 2018, 2:46pm UTC](https://discuss.elastic.co/t/newly-added-pipeline-does-not-appear-under-monitoring/121233 "2018-02-23T14:46:22Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![andreivasiletruta](https://avatars.discourse-cdn.com/v4/letter/a/35a633/32.png) [@andreivasiletruta](https://discuss.elastic.co/u/andreivasiletruta)\ **Post date:** [February 23, 2018, 2:46pm UTC](https://discuss.elastic.co/t/newly-added-pipeline-does-not-appear-under-monitoring/121233/1 "2018-02-23T14:46:22Z")
I have been adding under Management\>Pipelines a new pipeline and pressed the Save&Deploy. Note: the pipeline is jdbc based. I configured the logstash logs for debug. I checked the elastic logs too including the indices in the API call. In Kibana, under Monitoring \> Pipelines I only see the main one. Is there something that I missed? ![Screenshot_135](https://us1.discourse-cdn.com/elastic/original/3X/7/9/7951cc6501547ee30114ebe680a1b406a66611e8.png) Note: I am using the stack-docker ---
**Author:** ![shaunak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shaunak/32/6643_2.png) [@shaunak](https://discuss.elastic.co/u/shaunak)\ **Post date:** [February 23, 2018, 3:39pm UTC](https://discuss.elastic.co/t/newly-added-pipeline-does-not-appear-under-monitoring/121233/2 "2018-02-23T15:39:08Z")
What ID did you give the pipeline you created in _Management_ \> _Pipelines_? Do you see that ID anywhere in your Logstash logs? Also, is this ID also configured as the value of the `xpack.management.pipeline.id` setting in your `logstash.yml`? ---
**Author:** ![andreivasiletruta](https://avatars.discourse-cdn.com/v4/letter/a/35a633/32.png) [@andreivasiletruta](https://discuss.elastic.co/u/andreivasiletruta)\ **Post date:** [February 23, 2018, 3:42pm UTC](https://discuss.elastic.co/t/newly-added-pipeline-does-not-appear-under-monitoring/121233/3 "2018-02-23T15:42:38Z")
@shaunak I added a text based id and did not configure that xpack. I will try to figure out where to update. after setting the xpack key - do I need to restart the logstash process? 10x ---
**Author:** ![shaunak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shaunak/32/6643_2.png) [@shaunak](https://discuss.elastic.co/u/shaunak)\ **Post date:** [February 23, 2018, 3:44pm UTC](https://discuss.elastic.co/t/newly-added-pipeline-does-not-appear-under-monitoring/121233/4 "2018-02-23T15:44:20Z")
Yes, you will need to restart the Logstash process. You might also find this section in our docs helpful: [https://www.elastic.co/guide/en/logstash/current/configuring-centralized-pipelines.html](https://www.elastic.co/guide/en/logstash/current/configuring-centralized-pipelines.html) ---
**Author:** ![andreivasiletruta](https://avatars.discourse-cdn.com/v4/letter/a/35a633/32.png) [@andreivasiletruta](https://discuss.elastic.co/u/andreivasiletruta)\ **Post date:** [February 23, 2018, 3:46pm UTC](https://discuss.elastic.co/t/newly-added-pipeline-does-not-appear-under-monitoring/121233/5 "2018-02-23T15:46:06Z")
Thank you. If I started the stack-docker thus using docker-compose I need to follow the install xPack too? ---
**Author:** ![andreivasiletruta](https://avatars.discourse-cdn.com/v4/letter/a/35a633/32.png) [@andreivasiletruta](https://discuss.elastic.co/u/andreivasiletruta)\ **Post date:** [February 23, 2018, 3:47pm UTC](https://discuss.elastic.co/t/newly-added-pipeline-does-not-appear-under-monitoring/121233/6 "2018-02-23T15:47:46Z")
an apparently i can only use it - at least according to the docs - for a paid license. > feature that requires a paid X-Pack license ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 23, 2018, 3:47pm UTC](https://discuss.elastic.co/t/newly-added-pipeline-does-not-appear-under-monitoring/121233/7 "2018-03-23T15:47:51Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.