This monitor detects if there are problems with the Management Configuration service reading from the Operational Database. It indicates that the Management Configuration service does have access to the Operational Database, but is unable to calculate which objects need updated configuration because there is too much churn updates/deletes of objects due to a flood of discovery data.
This may happen if there is a flood of discovery data coming from all the Health Services at once and the database is still busy being updated on what objects have been discovered by each Health Service.
Check the database server health to ensure that it is under optimal performance conditions. If the database server is suffering from degraded performance or is not sized appropriately, this could be the cause for the Management Configuration service not being able to calculate which objects need updated configuration because each of the Collection Management Servers are constantly inserting discovery data.
Another problem could be that the Health Services are simply inserting too much discovery data. If this is the first time these objects are being discovered, this may be normal until everything has been discovered.
If this happening even after the initial deployment of agents and/or new Management Packs, contact Customer Support Services (CSS) with the name of this rule and the information from the state change event.