Open wiibaa opened 8 years ago
If by mistake the match config contains a hash instead of a valid string or array like this
grok { match => { a => { "b" => "c" } } }
Logstash fails to start with a cryptic error can't convert Array into String For a concrete example where a user can create this case and be lost, see https://discuss.elastic.co/t/filter-if-results-in-cant-convert-array-into-string-error/38805
Is there a mean for grok and this plugin to raise a better error message when the match config is invalid before jumping in config parser discussions.
If by mistake the match config contains a hash instead of a valid string or array like this
Logstash fails to start with a cryptic error can't convert Array into String For a concrete example where a user can create this case and be lost, see https://discuss.elastic.co/t/filter-if-results-in-cant-convert-array-into-string-error/38805
Is there a mean for grok and this plugin to raise a better error message when the match config is invalid before jumping in config parser discussions.