Migration process

Migrating from Monitoring Integrations 1.0 to 2.0 involves transitioning to an enhanced framework with improved scalability and management capabilities.

Prerequisites

Ensure the Monitoring Integration 1.0 configuration is disabled. See Identify Monitoring integrations 1.0 to identify if you are using 1.0 version of the integration.
Backup critical data, if any.

Migration Process

Navigate to the OpsRamp console and disable the Monitoring Integration 1.0 configuration.
In the Gateway, delete monitoring integration 1.0 app-dependent data from the repository and cache paths.

For NextGen Gateway

   cd /var/lib/rancher/k3s/storage/*default_content-home*/
   rm -rf repo/{app-name}
   rm -rf cache/{app-name}

For Classic Gateway

cd /opt/gateway/content/
rm -rf repo/{app-name}
rm -rf cache/{app-name}

Note

Replace {app-name} with the correct name of the app. For example, dell-power-max, dell-avamar, dell-power-store, hp-ux-server and so on.

Install the Monitoring Integration 2.0 app using the same IP and credentials as the previous 1.0 configuration.

Important

Ensure the Bypass Resource Reconciliation checkbox is not selected when configuring the Gateway profile.

Confirm that Monitoring Integration 2.0-related tar deployments are present in the repo/{app-name} folder. Use the following command to verify: cd /var/lib/rancher/k3s/storage/*default_content-home*/repo
Confirm that the Monitoring Integration 2.0 app is successfully collecting data. Verify that alert configurations and resources are properly mapped.
Uninstall the 1.0 integration, use the delete adaptor configuration API with the parameter skipDeleteResources=true

Post-migration

Ensure all resources are successfully linked to the Monitoring Integration 2.0 app.
Verify that templates are assigned and monitoring is actively running.
If issues arise, check OpsRamp logs or contact OpsRamp support.