[SERVER-45550] Allow hiding of specific startup warnings via config params Created: 14/Jan/20  Updated: 06/Dec/22  Resolved: 15/Jan/20

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

Type: Improvement Priority: Minor - P4
Reporter: Nic Cottrell Assignee: DO NOT USE - Backlog - Dev Tools
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-19790 Provide mechanism to clear/acknowledg... Backlog
Assigned Teams:
Developer Tools
Participants:
Case:

 Description   

Some production deployments are forced to run ext4 filesystems (for example) due to legal/licensing reasons. This causes a startup warning on every node. When using monitoring tools (such as Ops Manager), this can create false positives and admins may be tempted to disable startup warning checks completely.

I'm requesting a new configuration option to disable specific startup warnings, so that remaining warnings are true positives and don't spam Ops Manager alerts etc.

I envisage a new configuration file option like systemLog.hideWarnings which takes an array of strings like {{"dbPath-ext4"} that disables just the ext4 dbPath volume warning, but leaves all others in place.

This will require naming every warning and adding logic in startup_warnings_mongod.cpp and startup_warnings_common.cpp.



 Comments   
Comment by Carl Champain (Inactive) [ 15/Jan/20 ]

It's actually a duplicate of SERVER-19790.

Comment by Carl Champain (Inactive) [ 15/Jan/20 ]

Passing this ticket along to the appropriate team.

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