Template Changes Re-enable Disabled Components on Application Nodes

kenyamson

Hi,

Has anyone experienced this behavior?

I created an application template and assigned it to multiple nodes. For some nodes, I disabled certain components because they weren't applicable.

However, when I add a new component to the template, the previously disabled components on those specific nodes get re-enabled. I even tried deleting a component from a specific node, but it reappears after saving the template.

In the node's application settings, "Inherit from template" is not selected, so the component should stay disabled — but saving the template still re-enables it.

I'm on the latest version of SolarWinds and saw the same issue in version 2024.2. Is this expected behavior for SAM templates?

kenyamson

This doesn't work.

[embed:6b06e1a7-0ec1-4e43-9421-8caaf95469b6:40520406-1651-4785-918d-51599d5d394a:message=You%20can%20override%20the%20template%20settings%20at%20any%20time%20by%20disabling%20the%20Inherit%20From%20Template%20option%20for%20an%20individual%20application%20monitor%2C%20which%20breaks%20the%20inheritance%20relationship%20between%20the%20component%20monitor%20and%20its%20template.%20For%20example%2C%20credentials%20usually%20differ%20for%20each%20node%20so%20you%20can%20select%20a%20different%20credential%20for%20each%20assigned%20application%20monitor%2C%20thus%20overriding%20the%20template%20setting%20for%20the%20Credentials%20field.%0A%0ATo%20restore%20the%20inheritance%20relationship%20between%20a%20component%20monitor%20and%20its%20template%2C%20click%20Inherit%20From%20Template%20next%20to%20the%20setting.%0A%0A&type=information]

Use SAM application monitor templates and application monitors