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.

Note

The Opsview Agent is still supported, but we recommend that new and existing users deploying new monitoring use the ITRS Infrastructure Agent instead. The Opsview documentation version 6.8.4 or earlier remains a resource for Opsview Agent information.

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/custom/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

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 must set allowed_hosts in order for it to run if it is not automatically imported from the old Agent. See Infrastructure Agent Configuration for more information.

   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 been downloaded, open the file to install it.
4. Once the Agent is installed, you must set allowed_hosts for it to run if it is not automatically imported from the old Opsview Agent. For more information, see Infrastructure Agent Configuration.
5. You must manually set an inbound firewall rule to allow connections to come through:
   1. Open Windows Defender Firewall with Advanced Security or the Advanced settings of Windows Defender Firewall.
   2. Create a new inbound rule and perform the following steps in the rule wizard.
   3. Select the Program option.
   4. Set the program path to C:\Program Files\Infrastructure Agent\bin\infra-agent.exe.
   5. Select Allow the connection for actions to be taken.
   6. Select the appropriate networks based on your connectivity requirements: Domain, Private, and Public.
   7. Give the rule a name and select Finish.
6. Once Infrastructure Agent is running, you can uninstall the Opsview Agent.