-
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. Describe the solution you'd likeWe 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 consideredThere 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 contextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 3 replies
-
An example snippet of the logs: |
Beta Was this translation helpful? Give feedback.
-
FWIW, #2927 (comment) describes the different configuration options what fields to emit in the JSON log. You should be able to omit field |
Beta Was this translation helpful? Give feedback.
-
Thanks, that could be a good starting point! I'll look into it! |
Beta Was this translation helpful? Give feedback.
-
@johkin we will not guess what specifically is logged in your case. Please provide a complete JSON example. Given that #2927 exists and seeks to address the same fundamental problem, I'm moving this to a discussion. |
Beta Was this translation helpful? Give feedback.
-
The suggestion by @ansd work perfectly, thank you very much! |
Beta Was this translation helpful? Give feedback.
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).