Configuration file best practices
Zenoss recommends that you edit configurations through the Control Center browser interface. Using this method, edits are preserved and pushed to the Service Impact container when restarted. When Service Impact restarts, a new container is created. Any changes applied using the command are lost when Service Impact is restarted.
Use the Control Center browser interface to edit and preserve changes to /opt/zenoss_impact/etc/logback.xml. Modifying logback.xml in the Control Center browser interface requires a restart of the Service Impact service for the logging changes to take effect. If you use the command line to implement logging changes, they are implemented immediately; however, the changes made using the command line are lost when Service Impact is restarted.
The following sections describe how to edit Service Impact configuration files for Resource Manager 5.x and 4.2.x.