Action on a critical log about unusual memory configuration

[jang00777]

Impact of the bug This have an impact on critical log in unified page.

Describe the bug The bug(log) warn that there is a workflow configured with unusual memory setting. However mainly this is not about an any issue or error but just warning.

How to reproduce it Steps to reproduce the behavior: Check the critical log page. The log is reported from equalizer here

Expected behavior If these memory settings don't cause any problem on the system at all, it would be okay to remove a part sending log on the module

Additional context and error message For example, These tasks are configured with more memory than usual /pdmvserv_Run2016F_SingleMuon_UL2016_MiniAODv1_NanoAODv2_201215_091031_2514/DataProcessing, 5900 [MB] submitted requirement at original 2 core count /pdmvserv_Run2017E_HighMultiplicityEOF1_UL2017_MiniAODv1_NanoAODv2_201211_171117_1560/DataProcessing, 5900 [MB] submitted requirement at original 2 core count /pdmvserv_Run2018B_MET_UL2018_MiniAODv1_NanoAODv2_201212_053923_8234/DataProcessing, 5900 [MB] submitted requirement at original 2 core count /pdmvserv_Run2018C_EGamma_UL2018_MiniAODv1_NanoAODv2_210123_141603_6373/DataProcessing, 5900 [MB] submitted requirement at original 2 core count /pdmvserv_Run2018D_JetHT_UL2018_MiniAODv1_NanoAODv2_201214_114119_2058/DataProcessing, 5900 [MB] submitted requirement at original 2 core count

[github-actions[bot]]

Thanks for submitting your first issue