Backport PR #16495 to 8.15 branch, original message:

Release notes

Improved pipeline bootstrap error logs, it now includes the cause backtrace giving a hint where this issue occurred.

What does this PR do?

Any exceptions in the CompiledPipeline constructor during the input, filter and output setup will be re-thrown, with the message from the causing exception, but without the original stack trace. Sometimes, only the message isn't enough to identity form where the error is coming from, and adding the cause stacktrace to the logs would be useful for troubleshooting purposes.

Another option would be replacing the CompiledPipeline re-thrown exception stack trace, which is not recommended unless it's strictly necessary.

This PR adds the :cause errors details on the pipeline converge state error logs, which should shed light on those cases where the message isn't clear or does not describe the error source.

Why is it important/What is the impact to the user?

This PR gives users better visibility/understanding on pipeline's bootstrap errors.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files (and/or docker env variables)
• I have added tests that prove my fix is effective or that my feature works

How to test this PR locally

Try to start a failing/invalid pipeline configuration and check the logs out.

Related issues

• Closes Exceptions thrown in CompiledPipeline constructor lose stack trace context #16139