SaaS migration custom anomaly detection settings

[kurejko]

Hi,

while preparing a SaaS migration, we found in Managed a number of custom anomaly detection settings on host group or K8s cluster/namespace level.

As these entities are present in Managed only, what would be the best approach to migrate these settings to SaaS?

Migrate the OneAgents/K8s clusters first and then migrate the anomaly detection settings? Will the host group anomaly detection settings be available if no agents of that host group remain connected?

Or do we have to migrate that manually since the Managed host group/K8s namespace will have a different ID to the SaaS host group/K8s namespace anyway?

Thank you,

Jiri

[Julius_Loman · Accepted solution]

Hi Jiri,

If you don't change the host group during migration, the identifiers will be preserved, and you are good to go with deploying it using Monaco or any other automation utilizing Settings API in this case.

If you are planning some cleanup during migration, which might include hostgroup change, then you will need to do it manually (or semi-manually). 

The recommended way is to test your approach in some non-prod or lab environment to validate your migration scenario, so the saas upgrade will be smooth. 

Anyway, there are many configurations which must be recreated manually anyway, one of the most important is request naming rules, for example.