Key requests

[arild_palencia3]

Hi!
We are migrating from DT Managed to SaaS. Anyone knows what happens to the marked key requests during the config migration? We are using the oneagent re-route option.

Regards
Arild

[dannemca]

Your key requests will not be migrated, since they are part of Services entities and they will also be "new entities" in your SaaS.

https://docs.dynatrace.com/managed/upgrade/up-plan#data-migration

You can use Monaco, or play with APIs to make sure the same requests will be marked as Key Request in your SaaS env.

Example, you can list (get) all the current key requests you currently have in your Managed env, schemaid: builtin:settings.subscriptions.service, and then post it, for each service (objectid) once they are ready in SaaS env.

[Eric_Yu]

While migrating configurations, KeyRequests are associated to a specific Service ID. So, when re-routing the OneAgent traffic you'll have to check if the new Service ID on SaaS is the same one as the one in Managed (not likely).

If is not the same ID, you can either reconfigure KeyRequests for each service through the UI or, better, modify the scope (serviceId or objectId) during the migration of your Key Requests configuration (either Monaco or API).

https://docs.dynatrace.com/docs/shortlink/key-requests#manage-api

https://docs.dynatrace.com/docs/shortlink/api-v2-settings-get-schema

[dcryans]

Hi,

Often, service IDs will be the same in both tenants because of the algorithm that creates the ID.

But you are right, IDs may and will change during a migration
If you do not want to bother manually matching thousands of IDs across tenants, you may be interested in trying the Config Manager:
https://docs.dynatrace.com/managed/upgrade/up-execute-upgrade/up-migrate-cfg#config-manager

The config manager will match every type entity IDs using their properties (name, ip address, etc.), but also topology (relationships). Then they will be automatically replaced in your configs.