[SERVER-76558] Pure JSON logging in Resmoke Created: 26/Apr/23  Updated: 27/Oct/23  Resolved: 27/Oct/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Denis Grebennicov Assignee: [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive)
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Server Development Platform
Participants:

 Description   

Right now resmoke logs will look something like [...info..]{...json log...}. We have a request to make all resmoke logs json so that the output can be piped to jq ie:

{..info...json log...}

I want to better understand how jq is used as part of the developer workflow before we dive into this, but there are some good suggestions/stackoverflow posts in the comments to make note of during implementation.



 Comments   
Comment by Alya Berciu [ 02/May/23 ]

Adding some more context about why jq would be useful- sometimes you want to filter for particular log lines (which you can do easily enough with grep), but then you only care about one field in the log itself, e.g. attr.query. I wanted to use jq to quickly drill down to relevant information without constructing complex greps, or to pretty-print log lines so I could read all information more easily.

It would be cool (but probably not relevant to this ticket) if something like jq, or at least the ability to narrow down which parts of a log line you want to filter for, could be built into the evergreen parsley logger.

Comment by Alex Neben [ 26/Apr/23 ]

I am going to put this in the backlog for now. Please feel free to reply if you would like it to be higher priority. 

Generated at Thu Feb 08 06:33:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.