We have had a few bugs, which have been linked to this spike, that have reported shortcomings of the config drift monitor. These bugs have been closed as "not a bug" since they are technically not flaws in the intended functionality of the config drift monitor. However, given that we have had a few bugs reported concerning the scope of the config drift monitor, it is important to revisit the monitor's scope and understand if customer needs now necessitate an expanded scope or maybe a new solution to manage configuration drift altogether.

Working through this spike should give the team an opportunity to understand what the preferred path forward is to enhance the config drift monitor such that customers have a better experience and the team has less "not a bug" bugs to triage and respond to .

Done when:

• There is some understanding on how big of a customer pain-point the current scope of the config drift monitor is
• Jiras are mapped out to clarify the followup work needed as a result of this investigation (this will likely take the form of an enhancement or RFE)