Migrating from Opsview Agent

Prerequisites Copied

Note

The Infrastructure Agent can be used on monitored hosts with older Opsview versions, even if you do not upgrade to the latest version. However, we recommend that you upgrade to the latest version of Opsview to ensure that all changes, including security fixes and new features, will work correctly with the Infrastructure Agent.

Please consider the following before you proceed with the migration from Opsview Agent to Infrastructure Agent:

• The Opsview Agent is currently running on a Linux or Windows Server.
• An Infrastructure Agent package download is available for the required operating system.

Migration of configuration Copied

When upgrading from Opsview Agent to Infrastructure Agent, three settings in the configuration are sent over to the new agent on startup. These settings will be stored in cfg/imported.yml. If this file already exists, the Agent will not import the old settings on startup.

The settings are:

• allowed_hosts
• server port
• commands

The Agent will not import the following settings:

• allow_arguments
• allowed_ciphers
• allow_nasty_meta_chars
• ca
• certificate
• certificate_key
• file
• packet_count
• use_ssl

If you want to use these settings in the Infrastructure Agent, you need to transfer them over manually.

Migration procedure for Linux Copied

Warning

There are some known limitations when migrating configuration on Linux. The following are not supported:

• Combining multiple allowed_hosts directives.
• Multiple levels of include or include_dir recursion.

We recommend reviewing your migrated configuration after the process completes to ensure accuracy.

1. Stop the Opsview Agent service.

   sudo systemctl stop opsview-agent
   

   sudo systemctl disable opsview-agent
   

2. Upgrade the Opsview Agent using the instructions based on your OS. See Infrastructure Agent Installation.

3. Once the Agent is installed, you may update your configuration. For more information, see Infrastructure Agent Configuration. If your allowed_hosts setting was set in the old Agent, it will be automatically imported. If set to an empty list (allow all hosts), we recommend replacing it with an explicit list of permitted hosts.

   The agent may need to be restarted manually to use the changed configuration:

   sudo systemctl restart infrastructure-agent
   

4. Once the Infrastructure Agent is running, you can uninstall the Opsview Agent.

   For Debian and Ubuntu, run:

   sudo apt remove opsview-agent
   

   For OL and RHEL, run:

   sudo yum erase opsview-agent
   

Migration procedure for Windows Copied

1. Open Services, and then stop the Opsview Agent service.
2. Download the latest infrastructure-agent package from Agent Downloads.
3. Once the package has downloaded, open the file to install it.
4. Once the Agent is installed, you may want to update your configuration. For more information, see Infrastructure Agent Configuration. Your allowed_hosts setting will be automatically imported from the old Agent, if it is set. If set to an empty list (allow all hosts), we recommend replacing it with an explicit list of permitted hosts.
5. By default, no firewall rules are added. To allow Opsview to connect to the agent, select the desired firewall rules to add in the installer dialog. If installing using the command line, you can control which firewall rules are added by setting custom properties. For more information, see Windows Infrastructure Agent Installation.
6. Once Infrastructure Agent is running, you can uninstall the Opsview Agent.

If you encounter any issues during the migration, please refer to the Troubleshooting information.