[Fleet] Improve error handling for invalid ingest pipelines in YAML format #64739
Labels
Feature:EPM
Fleet team's Elastic Package Manager (aka Integrations) project
research
Team:Fleet
Team label for Observability Data Collection Fleet team
As we have made improvements and changes in this area, this issue is to research what happens now when Fleet attempts to install an invalid pipeline - do we fail gracefully and log an error?
Currently, when a package contains an ingest pipeline that is not accepted by Elasticsearch, EPM fails with an unhelpful error message.
This task is to improve the error message in a way that the user has a chance to understand what went wrong in the first place.
The underlying reason here is that the error we get from Elasticsearch is unhelpful, but we should at least catch it more gracefully, and point out that the ingest pipeline might be invalid.
See also #63726 & #72519 (comment)
The text was updated successfully, but these errors were encountered: