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
Is your feature request related to a problem? Please describe.
We are ingesting our RabbitMQ-logs as json into an ELK-installation, but according to the ECS-rules (or perhaps Elasticsearch) we are having trouble to parse the produced json.
The object "mfa" is an array with mixed contents with both String and Integer/Long.
Describe the solution you'd like
We would either like to see the mfa-object as a String-array or even better if one could specify to use the ECS standard in the generated json logs?
Describe alternatives you've considered
There are other tools that can modify the logs once they are produced, but it would easier to produce schema-compliant logs to start with.
Additional context
No response
The text was updated successfully, but these errors were encountered:
FWIW, #2927 (comment) describes the different configuration options what fields to emit in the JSON log. You should be able to omit field mfa (module function arguments) completely (if that's acceptable for you).
Is your feature request related to a problem? Please describe.
We are ingesting our RabbitMQ-logs as json into an ELK-installation, but according to the ECS-rules (or perhaps Elasticsearch) we are having trouble to parse the produced json.
The object "mfa" is an array with mixed contents with both String and Integer/Long.
Describe the solution you'd like
We would either like to see the mfa-object as a String-array or even better if one could specify to use the ECS standard in the generated json logs?
Describe alternatives you've considered
There are other tools that can modify the logs once they are produced, but it would easier to produce schema-compliant logs to start with.
Additional context
No response
The text was updated successfully, but these errors were encountered: