By wrapping reloader errors in a way that EA manager understands (i.e. in a MultiError of UnitError), newRunner initialization errors, including config parsing errors, will be surfaced and logged.
Checklist
- [ ] Update CHANGELOG.asciidoc I expect this to go into 8.17 first, then 8.16, but there may be uncertainty around this. We can add changelog before the release.
[ ] Documentation has been updated
How to test these changes
Start apm-server in EA managed mode (e.g. on ESS), pass in an invalid integration policy, e.g. setting apm-server.rum.response_headers to a string instead of a list. Check that in fleet UI that EA input unit has failed. Check that an error is logged.
Related issues
Fixes #14560
This is an automatic backport of pull request #14574 done by Mergify.
Motivation/summary
By wrapping reloader errors in a way that EA manager understands (i.e. in a MultiError of UnitError), newRunner initialization errors, including config parsing errors, will be surfaced and logged.
Checklist
- [ ] Update CHANGELOG.asciidocI expect this to go into 8.17 first, then 8.16, but there may be uncertainty around this. We can add changelog before the release.How to test these changes
Start apm-server in EA managed mode (e.g. on ESS), pass in an invalid integration policy, e.g. setting
apm-server.rum.response_headersto a string instead of a list. Check that in fleet UI that EA input unit has failed. Check that an error is logged.Related issues
Fixes #14560
This is an automatic backport of pull request #14574 done by Mergify.