â€‹After upgrading to r2.5 or greater, if the user edits a Monitoring Profile, created prior to CAPM r2.5, for say change detection rate or add/remote a metric family, and hits save, it may complain about invalid filter expression.
If the Monitoring Profile contains a metric family filter that has CONTAINS, it can throw an error during save.
In CAPM r2.5, we added a TYPE field to the definition of the FilterExpression for CONTAINS comparison.
During upgrade to CAPM r2.5+, we don't go and convert the existing FilterExpression to the new format, as the current format is still honored.
It's not until the Monitoring Profile is saved, do we check that it follows the new syntax.
Original defect: DE262647 / Case 00450175
If a customer wishes to edit a Monitoring Profile created before CAPM r2.5, they should first edit the filters on the Monitoring Profiles.
They just need to open the filter and hit save. It will convert it to the new format automatically.
Then the customer can edit the Monitoring Profile itself to make other changes as they tried before.