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
{{ message }}
This repository has been archived by the owner on Mar 14, 2019. It is now read-only.
yeah - using a logging pattern to output lines of text in json format.
We've 3 choices
treat all logs as a single line of text (so no category / time / thread / breadcrumb)
we log random output using arbitrary formats (whatever log4j.properties wins) then folks manually try figure out the regex expressions to then be able to parse into fields for dumping into Elasticsearch
we log as json so that automatically all logs go nicely into Elasticsearch with no dodgy regex to maintain; and all the values such as breadcrumbs/threads/categories/levels are all nicely searchable
If we had a nice json log viewer, we could then do a nice coloured tail program so folks get nicer text output on their shells (properly colouring info/err/warning lines etc)?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
for java/karaf/tomcat/wildfly images we should default to use JSON logging so that things just work nicely with logstash and elasticsearch?
The text was updated successfully, but these errors were encountered: