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
I've come across your Docker image. It's very handy.
A feature request:
All the messages currently consist of very common words, and the entire sentence is fixed and repeated. When they are mixed with tons of other applications' logs in a data lake (e.g., in Elasticsearch, Datadog, Splunk, etc.), it is very hard to query for a particular message from your running container.
So, why not append each message with a dynamically generated random string -- each log line has a different, unique string. That will give the best of both worlds:
You can query for the fixed part of your current message in order to get all messages from your particular container.
You can also query for that random string to pinpoint a particular occurrence of a message.
The text was updated successfully, but these errors were encountered:
Thank you for your interest, this sounds like a interesting feature to implement. if I understand correctly it would be nice to have something like this:
You also want a fixed portion of string per line. So, not the entire message body is a random string, but more like:
2018-03-02T22:33:27-06:00 ERROR An error is usually an exception <random-string>
2018-03-02T22:33:27-06:00 INFO This is less important than debug <random-string>
...
That way, I can search by either the fixed portion of the log line, or the unique-per-line random string.
I've come across your Docker image. It's very handy.
A feature request:
All the messages currently consist of very common words, and the entire sentence is fixed and repeated. When they are mixed with tons of other applications' logs in a data lake (e.g., in Elasticsearch, Datadog, Splunk, etc.), it is very hard to query for a particular message from your running container.
So, why not append each message with a dynamically generated random string -- each log line has a different, unique string. That will give the best of both worlds:
The text was updated successfully, but these errors were encountered: