[SERVER-48441] Put assertion and log severity selection policy into a readme in the source tree Created: 27/May/20  Updated: 06/Dec/22  Resolved: 13/Jan/22

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

Type: Task Priority: Major - P3
Reporter: Andy Schwerin Assignee: Backlog - Security Team
Resolution: Duplicate Votes: 0
Labels: former-quick-wins, neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-62595 Migrate logv2/README.md to docs/loggi... Closed
is duplicated by SERVER-63184 Update and combine docs/logging.md an... Needs Scheduling
Related
is related to SERVER-46547 Update Server Logging Rules and move ... Closed
Assigned Teams:
Server Security
Sprint: Service arch 2020-06-01, Service arch 2020-06-15, Service arch 2020-06-29, Service arch 2020-07-13
Participants:

 Description   

We should write down the policy for when to use which assertion macro, and for how to choose a log severity level, and put it in a readme file in the mongodb/mongo source tree.


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