# Elastic Cloud Ingest Pipeline Change
**URL:** https://discuss.elastic.co/t/elastic-cloud-ingest-pipeline-change/300365
**Category:** Elasticsearch
**Tags:** ingest-pipeline
**Created:** [March 22, 2022, 3:58pm UTC](https://discuss.elastic.co/t/elastic-cloud-ingest-pipeline-change/300365 "2022-03-22T15:58:11Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@kinderrs](https://discuss.elastic.co/u/kinderrs)
#### Post date: [March 22, 2022, 3:58pm UTC](https://discuss.elastic.co/t/elastic-cloud-ingest-pipeline-change/300365/1 "2022-03-22T15:58:11Z")
Hi all! I am using Elastic Cloud to collect information from a custom log. I created a ingest pipeline but then found that I had to change/update a portion of the pipeline (a dissect processor) which went from something like:
```auto
%{source.ip} %{?user.ident} %{?user.name} [%{@timestamp}] \"%{http.request.method} %{url.original} HTTP/%{http.version}\" %{http.response.status_code} %{http.response.body.bytes}
```
to something like
```auto
%{source.ip} %{?user.ident->} %{?user.name} [%{@timestamp}] \"%{http.request.method} %{url.original} HTTP/%{http.version}\" %{http.response.status_code} %{http.response.body.bytes}
```
to compensate for the user.name field being prefixed with a space by user input. After updating that pipeline processor, are there steps that need followed to kick start the ingestion of data again because currently all I am seeing is filebeat connecting to a backoff url repeatedly while the log on the machine keeps getting new data added to it.
Thanks!
---
### Author:  [@stephenb](https://discuss.elastic.co/u/stephenb)
#### Post date: [March 23, 2022, 1:27am UTC](https://discuss.elastic.co/t/elastic-cloud-ingest-pipeline-change/300365/2 "2022-03-23T01:27:42Z")
Hi @kinderrs Welcome to the community.
As soon as you post the new pipeline it will start being used.
What exactly is the filebeat error?
Changing a pipeline does not usually affect the connectivity.
Did you accidentally rename the pipeline?
---
### Author:  [@kinderrs](https://discuss.elastic.co/u/kinderrs)
#### Post date: [March 23, 2022, 1:41pm UTC](https://discuss.elastic.co/t/elastic-cloud-ingest-pipeline-change/300365/3 "2022-03-23T13:41:18Z")
You're right, it does get used immediately. I finally found where I could turn on debug mode for the integration (in this case custom logs) and lo and behold a programmer had created his/her own format for the log on one of the servers this ingest pipeline was handling which gummed up the works for just about everything. I am considering just removing the policy from the offending machine and creating a custom pipeline for the "custom" log.
I appreciate the response and the confirmation of a suspicion that there was nothing to do and something else was wrong.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 20, 2022, 1:42pm UTC](https://discuss.elastic.co/t/elastic-cloud-ingest-pipeline-change/300365/4 "2022-04-20T13:42:12Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.