[SERVER-56103] Add new "Assert" log component Created: 14/Apr/21  Updated: 01/Aug/22  Resolved: 09/Aug/21

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

Type: Improvement Priority: Major - P3
Reporter: Randolph Tan Assignee: Tyler Seip (Inactive)
Resolution: Done Votes: 0
Labels: sa-groomed
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-68463 [6.0] replsets/profile.js fails to se... Closed
related to SERVER-56043 Log the error when retrying in auto_r... Closed
Sprint: Service Arch 2021-08-09, Service Arch 2021-08-23
Participants:
Linked BF Score: 35
Story Points: 1

 Description   

And change component of assert_util.cpp from "default" to "assert".

 

The primary motivation is to enable some of our test suites to enable logging asserts without bloating the logs.

 

Acceptance criteria:

Discuss the ticket with the reporter and write up possible solutions that we can pick from. 

 



 Comments   
Comment by Randolph Tan [ 09/Aug/21 ]

Hm... no objections on the idea. On the other hand, I'm not sure if I'll be able to take advantage of that feature. Perhaps asking a wider audience would be a better judge of whether it would be something worth spending time on.

Comment by Tyler Seip (Inactive) [ 09/Aug/21 ]

As follow up work to these changes, we might want to consider adding a separate tag system to our logging which would allow us to, e.g., tag something as an assertion while also giving it a different log component, which would allow us to filter by any combination of component and/or tag. renctan, what do you think of this idea?

Comment by Githook User [ 09/Aug/21 ]

Author:

{'name': 'Tyler Seip', 'email': 'Tyler.Seip@mongodb.com', 'username': 'tseip-mongo'}

Message: SERVER-56103: Add kAssert log component and use it in assert_util
Branch: master
https://github.com/mongodb/mongo/commit/9f3fa9fd6a833759239aae722e4a1f122ca246ff

Generated at Thu Feb 08 05:38:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.