1 of 1 people found this helpful
Re-posting excerpt from an older aLTeReGo discussion
Baseline changes made at the template level break inheritance after seven days of data has been collected. The only way to revert the change is to go into the assigned application and re-inherit from the template.
The recommendation for expediency's sake would be to remove the template/applications from the nodes and re-apply it to the nodes. As stated above, once inheritance is broken at the application level, the only way to re-inherit the settings back from the template is by editing the assigned application for each of the 3 applications across 100+ nodes in your case. Unfortunately changing this via the database is not a simple task. It is indeed possible, though I would not recommend it. If you'd like to attempt it anyway though it's strongly suggest to back up your database beforehand. The SQL contained in the reports below should get you pointed in the right direction with inheritance.
APM Component Monitors that are not Inheriting from their Original Template
APM Component Monitors Whose Credentials are not Inherited from the Original Template