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
We know that the awesome_print project is slow to release new versions.
Given that the Logstash Event only supports a fixed number of datatypes, I propose that we use simple ERB style templating to build a string representation of an Event.
One change that immediately comes to mind is to sort flat map the output and use the nested field reference style of key naming. This will encourage users to become familiar with it.
e.g.
We know that the awesome_print project is slow to release new versions.
Given that the Logstash Event only supports a fixed number of datatypes, I propose that we use simple ERB style templating to build a string representation of an Event.
One change that immediately comes to mind is to sort flat map the output and use the nested field reference style of key naming. This will encourage users to become familiar with it.
e.g.
The text was updated successfully, but these errors were encountered: