You can move the integration configuration from one gateway to another.
Scenario: Suppose you have a gateway monitoring VMware vCenter or IBM Storwize, and you come to know that your gateway is overloaded (monitoring beyond its capability). You decided to move some of the integrations from the overloaded gateway to another gateway.
Follow the below steps:
- Navigate to Setup > Account > Integrations.
- From the Installed Integrations page, select the required gateway-based integration.
- Search for the integration and click the three dots (menu) icon and click Edit.
- Select a gateway from the Collector Profiles drop-down list.
- Click Finish.
Note:
- Before you change the gateway profile, make sure both gateways are connected to OpsRamp. Re-discover and manage the resources with the existing gateway first before switching to another gateway.
- Integration migration from one gateway to another works for Classic Gateway, NextGen Gateway, and Windows Gateway.
- Any open critical or warning alerts generated by the previous gateway will not get a HEAL alert after switching to the new gateway because the newly added gateway will not contain the monitoring history of the previous gateway.
Limitation
Integration migrations work for all the Classic Gateway integrations like SNMP, SSH, VMWare, WMI, and so on, but do not work for SKD-based applications and integrations.