Configuration Monitoring Filter Bug

posted Oct 6, 2017, 9:32 AM by Eric Patrick
The configuration monitoring infrastructure has been updated to handle the rare use case where filtered configuration conflicts with non-filtered configuration. The resolution is to sort configuration entry queries by filter.

For example, given a QBO3 site with Filter = "Release 2017.10.01"
  • Add a statement called ConfigurationTest, applied to the filter "Release 2017.10.01"
  • Add a statement called ConfigurationTest, applied to the entire database
The expected behavior is that the first version of the statement (filter = "Release 2017.10.01") will "win". Until this fix, the results were essentially random.

Comments