Introduction

Migrating an integration from Monitoring Integration 1.0 to Monitoring Integration 2.0 is a crucial process to leverage the updated features of Migration integrations 2.0. This process requires careful planning and attention to ensure a seamless transition.

Key points to consider

  1. Irreversible Process: Once migration begins, it cannot be reverted.
  2. Handling Customizations:
    • Any customizations in Monitoring Integration 1.0 (e.g., metrics) must be manually replicated in Monitoring Integration 2.0 configurations before the migration.
    • Clone the global Device Management Policies (DMPs) and templates of Monitoring Integration 2.0 to replicate the customizations.
    • Refer to the following guide for cloning and customizing DMPs and templates:
      Clone Device Management Policies (DMPs) and Templates.
  3. The Monitoring Integration 1.0 app will cease to function once the migration begins.
  4. Monitoring and discovery might pause temporarily depending on the number of resources being migrated.
  5. Criteria for Successful Migration:
    • All Monitoring Integration 1.0 resources must be linked to the Monitoring Integration 2.0 app.
    • Templates must be assigned automatically through the DMP flow, and monitoring should resume.

Steps for migration

Prerequisites

  • Ensure the Monitoring Integration 1.0 configuration is disabled.
  • Backup any critical data if required.
  1. Disable the Monitoring Integration 1.0 app configuration from the OpsRamp console.
  2. Log in to the Gateway and delete Monitoring Integration 1.0 app-dependent data from the repository and cache paths.

Commands for NextGen Gateway

   cd /var/lib/rancher/k3s/storage/*default_content-home*/
   rm -rf repo/dell-power-store
   rm -rf cache/dell-power-store

Commands for Classic Gateway

cd /opt/gateway/content/
rm -rf repo/dell-power-store
rm -rf cache/dell-power-store

Note: In the code above, replace dell-power-store with the app name if migrating another app.

  1. Install the Monitoring Integration 2.0 app and configure it with the same IP and credentials as the Monitoring Integration 1.0 configuration. Important: Do not enable the Bypass Resource Reconciliation checkbox while selecting the Gateway profile.
  2. 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

  1. Ensure that discovery and monitoring functions continue with the Monitoring Integration 2.0 app.
  2. Once validation is complete, delete the Monitoring Integration 1.0 configurations and uninstall the app using API calls. To use the following API calls, you should have an OAuth 2.0 key and secret.
  3. Delete the configuration one by one through the delete adaptor config API with the request parameter as skipDeleteResources=true

Endpoint: https://{{host}}/api/v2/tenants/{tenantId}/integrations/installed/config/{configId}?skipDeleteResources=true

Request Body:

{
  "uninstallReason": "Migration to Monitoring Integration 2.0",
  "skipDeleteResources": true
}
  1. Uninstall the adaptor application through API with skipDeleteResources=true in the post request.

End-Point: https://{{host}}/api/v2/tenants/{tenantId}/integrations/installed/{installedIntgId}

Request Body:

{ 
"uninstallReason": "Migration to SDK 2.0", 
"skipDeleteResources": true 
}

Post-migration

  • Verify that all resources are linked to the Monitoring Integration 2.0 app.
  • Confirm that templates have been assigned and monitoring is active.