To help readers assess the impact of identified metadata inconsistencies on sharded clusters, the checkMetadataConsistency command results should include a severity assessment for every identified inconsistency. The business impact of these inconsistencies can range from negligible to very significant.

The following 3-level semantic is suggested for the severity field:

• high: Poses a severe risk to business operations, including potential data loss. Immediate and urgent action is essential.
• medium: Currently poses a limited risk to business operations. However, performing DDL operations on affected collections could intensify the metadata divergence.
• low: Represents known metadata inconsistencies that do not impact business operations (e.g., CollectionUUIDMismatch on config.system.sessions).

The following is an example of command results that include a set severity:

"runResult": [
    {
        "type": "CollectionUUIDMismatch",
        "description": "Found collection on non primary shard with mismatching UUID",
        "details": {
            "namespace": "config.system.sessions",
            "shard": "atlas-s9i6vx-shard-0",
            "localUUID": {
                "$binary": {
                    "base64": "BOuFwIPiRkeThLvt415Y/w==",
                    "subType": "04"
                }
            },
            "uuid": {
                "$binary": {
                    "base64": "Xe1X3YKiRFOpLD3VMiCADA==",
                    "subType": "04"
                }
            },
            "numDocs": 409,
            "severity": "low"
        }
    }
]