Ingest Pipeline ID not working for UDP Integration


We are using the Custom UDP integration in Fleet to ingest logs from Untangle firewalls.

I've created an ingest pipeline, called Untangle, that should parse the message field sent over from the integration.

When I test the pipeline in the UI it works as intended.

Also, if i run POST logs-udp.untangle-default/_update_by_query?pipeline=Untangle, it also works correctly.

The issue is if i add the pipeline id to the integration, it does not work. Are there any known issues around adding pipeline id to the custom UDP Integration?



Its because the beats code lowercases the pipeline name and Elasticsearch is case sensitive. See

1 Like

Wow, I spent way too much time on this. Works with lowercase, thanks.

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