Early JSON logging implementation #4917
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
About the pull request
Explain why it's good for the game
A simple JSON logging implementation for feeding in logstash/opensearch because:
While our current usage of OpenSearch with legacy HTML-hybrid logs is great for fulltext searching about anything, it immensely falls short when you want to obtain data in a structured fashion (eg ahelp tickets text), filtering by id (eg ahelp lines by sender), or want to do aggregations (eg round results)
Just a sample impl for testing this workflow, it's incomplete, not well enough thought out (defines? port another backend instead?), and only contains a few log lines right now