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
extractors/pipeline make regex-replace capable to insert new-line/carriage-return #5225
Comments
I put my two cents at the issue. I'm using graylog to feed it with multiline messages from php-fpm slow logs. And it's really hard to read messages like these
And there is no way to configure php-fpm produce logs in json or any other format, so extracting this ugly message into normal stacktrace like this
will be really usefull. |
I was pointed here when posting at https://community.graylog.org/t/using-extractor-to-create-a-field-that-gets-displayed-with-newlines/7325/4 -- I posted a bookmarklet there to handle this client-side. Would anyone be able to point me at the code where this could be handled so I can try and understand where the problem arises from? |
Note that this was once possible, at least as per: #1956 |
It maybe may works for you: #5971 (comment) |
Expected Behavior
When using regex-replace you should be able to create a multiline message by replacing characters with a new line.
Look into this example:
Inserted Content of one field:
Should become the following after replacement of
__
to\n
or similar.The current regex-replace only allow something like, that is not the intention of this replacement.
Context
When receiving data from sources where formatting is limited but the information should be more readable for humans formatting options should work in a very basic way. Creating single fields would only make sense when sub-fields are possible.
This is simple to make messages more readable to humans.
Your Environment
The text was updated successfully, but these errors were encountered: