Bug 2256725

Description of problem (please be detailed as possible and provide log
snippests):
===================================================================================
Below MDSCacheUsageHigh alert is fired when MDS cache usage breaches 95% of the mds_cache_memory_limit but the alert does not provide clear instructions or steps to take in response to the alert. 

The alert should include a call to action, providing either steps to increase the memory request for MDS pods or a link to the documentation on what to do when the cache oversize alert is received.


Alert:

Name
MDSCacheUsageHigh

Severity
Critical

Description

MDS cache usage for the daemon mds.ocs-storagecluster-cephfilesystem-b has exceeded above 95% of the requested value. Increase the memory request for mds.ocs-storagecluster-cephfilesystem-b pod.

Message
High MDS cache usage for the daemon mds.ocs-storagecluster-cephfilesystem-b.


Version of all relevant components (if applicable):
odf version: 4.15.0-102


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?
Yes

Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:
No, this is a new feature in 4.15

Steps to Reproduce:
===================
1) Create 3m, 3w OCP cluster and install ODF on it.
2) Create multiple cephfs PVCs with RWX access mode
3) Attach multiple pods to those PVCs and start continuous file creation + meta data operations 
4) wait till MDS cache usage breaches 95% and the alert to fire

Actual results:
===============
The MDSCacheUsageHigh alert is lacking a call to action

Expected results:
=================
The alert should include a call to action, providing either steps to increase the memory request for MDS pods or a link to the documentation on what to do when the cache oversize alert is received.