[SERVER-80367] Set all virtual collection query logs to be DEBUG level Created: 24/Aug/23  Updated: 27/Oct/23  Resolved: 19/Sep/23

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

Type: Task Priority: Minor - P4
Reporter: Matthew Kim Assignee: Chris Wolff
Resolution: Gone away Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-74368 Reduce log verbosity for virtual coll... Closed
Assigned Teams:
Query Integration
Participants:

 Description   

As part of SERVER-74368, work was done to reduce log verbosity for virtual collection queries. The create/drop collection logs were set to be DEBUG for virtual collections, and the "Named pipe is closed" log was deduplicated. 

At this point, the ADF (Atlas Data Federation) + compute mode mongod system has been stable for a while, and we can set all virtual collection query logs to be DEBUG level to reduce the number of logs we output and ultimately reduce pressure on the splunk instances. 

Update:
Please, note that we have ERROR/WARNING/INFO/DEBUG1-5 log levels and we can disable logging only for DEBUG levels. "Named pipe is closed" log messages was an INFO level, which potentially pollute logs in splunk instances.



 Comments   
Comment by Yoon Soo Kim [ 19/Sep/23 ]

This is resolved by the commit: https://github.com/mongodb/mongo/commit/3fdd9c6c3e71e9be3478f840afab8eea93c2061c#diff-91247866d18d630e72069e47780e873fcf659460ba0528b4e93bf2996f93c321

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