Golden rules for configuration and operation of censhare.
No tests on productive systems
Use the test system. Test new features, clients, plug-ins and other changes always on a test system first.
-
Any untested configuration change or system component can cause performance problems or errors.
Updates and changes only with low server load
Perform configuration updates/changes with the censhareAdmin always at times of low server load.
-
Updates that are passed on to the client, can lead to performance problems or errors.
Run comprehensive master data changes always at times of low server load.
-
Changes can have unexpected effects on many assets and the cache database and thereby lead to performance problems.
Comment your changes
For configuration changes in modules and services always leave a comment in the comment box. Ideally with date and ticket ID, if available.
-
It makes it possible to assign subsequent problems to the change.
Monitor file systems
Monitor the utilization of file systems.
-
Full file systems will cause performance problems, errors or system downtime.