-
Notifications
You must be signed in to change notification settings - Fork 186
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
Render leading whitespace in log messages #140
Comments
Can you please share a screenshot of the logtrail and a sample ES document ? Make sure you hide confidential info. |
Original logs as viewed in Kibana (out of order): Renders like (in order but all indentation scrubbed): |
@dbsanfte I see that each line in the json object is interpreted as an event. I would recommend you to use logstash to format the event and map the whole json doc to a field in event or extract multiple fields from json. https://www.elastic.co/guide/en/logstash/current/plugins-filters-json.html |
I had a dig into your suggested solution, but no dice. The main problem is that multiline-gelf isn't supported in Logstash. The multiline codec doesn't work with gelf, and the multiline filter was deprecated in logtash versions 5.x. logstash-plugins/logstash-input-gelf#37 In the meantime is there any way to get Logtrail to honour the leading whitespace? |
Actually nevermind. I was able to edit the css to 'white-space: pre', but some messages are out of order and the JSONs aren't rendered right. I guess I'll need to wait for multiline gelf support in Logstash. Thanks for the response. :) |
Great. I was about test similar changes before proposing! |
Added white-space: pre-word in CSS for message |
We have a lot of log messages that are indented as part of "prettifying" JSONs. These show up fine in Kibana, so the leading whitespace is there, but Logtrail strips it out when it renders it in the browser. This makes our logs a lot less pretty (the JSONs are flat and ugly).
Can we have some sort of option for Logtrail to render the leading whitespace in our log messages?
Cheers :)
The text was updated successfully, but these errors were encountered: