You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This happens at least with filebeat, when a module configuration contains settings of an unexpected type, a full stack trace is printed instead of just the error message. It should print only a error message indicating the problem with the configuration.
For confirmed bugs, please report:
Version: 7.x (at least)
Steps to Reproduce: For example in the following configuration, the ssl config should be passed as a yaml-formatted string, not as an object:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Hi!
We just realized that we haven't looked into this issue in a while. We're sorry!
We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!
This happens at least with filebeat, when a module configuration contains settings of an unexpected type, a full stack trace is printed instead of just the error message. It should print only a error message indicating the problem with the configuration.
For confirmed bugs, please report:
When starting filebeat with this config, it exits with a trace like the following one:
There is a similar issue with export subcommands #17769.
The text was updated successfully, but these errors were encountered: