# How to stop logstash using default address when using pipeline

**URL:** <https://discuss.elastic.co/t/how-to-stop-logstash-using-default-address-when-using-pipeline/308922>\
**Category:** Logstash\
**Created:** [July 5, 2022, 2:00pm UTC](https://discuss.elastic.co/t/how-to-stop-logstash-using-default-address-when-using-pipeline/308922 "2022-07-05T14:00:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![michael.rhys](https://avatars.discourse-cdn.com/v4/letter/m/d6d6ee/32.png) [@michael.rhys](https://discuss.elastic.co/u/michael.rhys)\
**Post date:** [July 5, 2022, 2:00pm UTC](https://discuss.elastic.co/t/how-to-stop-logstash-using-default-address-when-using-pipeline/308922/1 "2022-07-05T14:00:06Z")

</div>

I am configuring logstash inside kubernetes using the pipeline and it is connecting to my central elk stack fine.

However not only is it connecting to the ELK Host I specify it is repeatedly trying to contact [http://elasticsearch:9200/](http://elasticsearch:9200/) which is generating an error and filling up the log files.

How can I stop logstash trying to send requests to this address.

I am using a config map for my logstash configuration. This requests seems to be coming from the default config/logstash.yml but I cannot edit this file as any changes made outside the ConfigMap are not persistent.

---

<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:** [August 2, 2022, 2:00pm UTC](https://discuss.elastic.co/t/how-to-stop-logstash-using-default-address-when-using-pipeline/308922/2 "2022-08-02T14:00:24Z")

</div>

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