Common problems with non-standard solutions

Overview

We understand the wish to adapt the server running Monitor to adhere to internal requirements. Since the server is set up with root access available, it's no doubt tempting to modify the system to ones own liking. In this article we will list some use cases that we strongly advice against. These solutions will compromise the reliability of the product to the point where we cannot provide full support.

We recognise that some customers will require these or similar modifications, even though we do not recommend them for a standard installation. In these cases we only support changes made directly by our Professional Services team. Subsequent support of related problems on these systems will only be available through Professional Services and not through the Support team.

Root access

It's worth noting that root access is something that will eventually be removed. Working with the standard setup is, therefore, a good habit that will eventually be enforced.

Using Active Directory to manage system users

Use case

Some organizations require that system users are replaced by users managed by Active Directory. These would include the users monitor and/or apache.

Recommendation

This is not recommended and will cause severe problems.

Running different versions of RHEL on different nodes

Recommendation

OP5 Monitor is designed to run on nodes with the same OS version. For example, using RHEL 6 on some nodes and RHEL 7 on others is not supported. For best reliability, the same point release should be used on all nodes, i.e. RHEL 7.6.

Rationale

We simply can't test all different configurations. The expected behavior is to regularly update the whole system with yum update, including both Monitor specific packages as well as the underlying system.

Running different versions of Monitor of different nodes

Recommendation

Neither is running different versions of Monitor supported. All nodes must run the same minor release, and if possible, the same micro release.

Rationale

See the point above.

Using a third-party load balancer

Recommendation

It's not supported to run any load balancing on the OP5 Monitor servers outside of the build in functionality for the purpose. This will cause severe breakage.

Rationale

Outside of the built-in load balancing, OP5 Monitor can't keep track of what node is reporting what data if it comes from different IP's.

Using a customized php.ini

Recommendation

It's not supported to use a customized php.ini. This may lead to various problems in the GUI. However, the following settings may be increased if you encounter problems in GUI:
php.ini

memory_limit
max_execution_time

Rationale

It's very hard to give support on customized PHP configurations. We have received many tickets where the root cause was a customized php.ini.

SELinux

Recommendation

It's not supported to enable SELinux on the OP5 Monitor servers. This will cause severe issues.

Rationale

OP5 Monitor is not tested together with SELinux and SELinux is set to disabled during the installation of OP5 Monitor.