Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pipeline generator expects error message field to always be string #327

Closed
P1llus opened this issue Apr 19, 2021 · 1 comment
Closed

Pipeline generator expects error message field to always be string #327

P1llus opened this issue Apr 19, 2021 · 1 comment
Labels
bug Something isn't working enhancement New feature or request

Comments

@P1llus
Copy link
Member

P1llus commented Apr 19, 2021

Certain modules has multiple error messages, so the error.message field returned might have more than a single value (an array of multiple values).

The code on this line: d74415f#diff-3a1cbf8695454ceffdb9bbb280ad58c06e82c70cdc8a420700b3804196fc8ce5R338

That was added with #290.

An example would be this PR elastic/integrations#783 (commit f929437), which when running the generator will return:

suricata/eve test-eve-small.log:
[0] can't unmarshal event to check pipeline error: json: cannot unmarshal array into Go struct field .Error.Message of type string

Is it possible to add support for arrays/slices here as well?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants