<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Settings that cannot be migrated with “Dynatrace-Config-Manager” in Upgrade to SaaS</title>
    <link>https://community.dynatrace.com/t5/Upgrade-to-SaaS/Settings-that-cannot-be-migrated-with-Dynatrace-Config-Manager/m-p/232275#M159</link>
    <description>&lt;P&gt;Honestly, if you are looking to upgrade from Managed to SaaS, I would partner directly with Dynatrace. Open a support ticket with the ask and the should be able to assist you in exporting the current settings/posture of your managed instance and then import it into your newly created SaaS instance.&amp;nbsp;&lt;/P&gt;&lt;P&gt;A cool link populated to check out as well:&amp;nbsp;&lt;A href="https://www.dynatrace.com/platform/saas-upgrade/?_ga=2.189722667.1476650388.1702901257-1341078005.1692102269&amp;amp;_gl=1%2a1ppzrqi%2a_ga%2aMTM0MTA3ODAwNS4xNjkyMTAyMjY5%2a_ga_1MEMV02JXV%2aMTcwMjkyNTQ5Mi4xOTEuMS4xNzAyOTI1NzE1LjAuMC4w" target="_blank"&gt;https://www.dynatrace.com/platform/saas-upgrade/?_ga=2.189722667.1476650388.1702901257-1341078005.1692102269&amp;amp;_gl=1%2a1ppzrqi%2a_ga%2aMTM0MTA3ODAwNS4xNjkyMTAyMjY5%2a_ga_1MEMV02JXV%2aMTcwMjkyNTQ5Mi4xOTEuMS4xNzAyOTI1NzE1LjAuMC4w&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 18 Dec 2023 18:57:04 GMT</pubDate>
    <dc:creator>ChadTurner</dc:creator>
    <dc:date>2023-12-18T18:57:04Z</dc:date>
    <item>
      <title>Settings that cannot be migrated with “Dynatrace-Config-Manager”</title>
      <link>https://community.dynatrace.com/t5/Upgrade-to-SaaS/Settings-that-cannot-be-migrated-with-Dynatrace-Config-Manager/m-p/231867#M157</link>
      <description>&lt;P&gt;I understand that the released “Dynatrace-Config-Manager” is a very powerful migration tool. However, I imagine that there are settings that cannot be migrated with this tool. I'm looking for information about settings that cannot be migrated with this tool.&lt;/P&gt;&lt;P&gt;&lt;A href="https://github.com/Dynatrace/Dynatrace-Config-Manager/releases/tag/v1.0.1" target="_blank"&gt;https://github.com/Dynatrace/Dynatrace-Config-Manager/releases/tag/v1.0.1&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 14 Dec 2023 09:01:57 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Upgrade-to-SaaS/Settings-that-cannot-be-migrated-with-Dynatrace-Config-Manager/m-p/231867#M157</guid>
      <dc:creator>Shirai</dc:creator>
      <dc:date>2023-12-14T09:01:57Z</dc:date>
    </item>
    <item>
      <title>Re: Settings that cannot be migrated with “Dynatrace-Config-Manager”</title>
      <link>https://community.dynatrace.com/t5/Upgrade-to-SaaS/Settings-that-cannot-be-migrated-with-Dynatrace-Config-Manager/m-p/232262#M158</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/32074"&gt;@Shirai&lt;/a&gt;,&lt;BR /&gt;&lt;BR /&gt;It will support all settings supported by the Terraform Provider:&lt;BR /&gt;&lt;A href="https://registry.terraform.io/providers/dynatrace-oss/dynatrace/latest/docs" target="_blank" rel="noopener"&gt;https://registry.terraform.io/providers/dynatrace-oss/dynatrace/latest/docs&lt;/A&gt;&lt;/P&gt;&lt;P&gt;- Except for Account level settings and Access tokens&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Some settings are not supported by APIs, these settings will not be supported by any tool.&lt;BR /&gt;There is no official list, as it keeps changing&lt;/P&gt;&lt;P&gt;Here are ones that I know of:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Web Request Naming rules for Services (Any service &amp;gt; Settings &amp;gt; Request naming rules)&lt;/LI&gt;&lt;LI&gt;Mobile/Custom application naming rules (Any mobile/custom application &amp;gt; Settings &amp;gt; Naming rules)&lt;/LI&gt;&lt;LI&gt;Mobile/Custom/Web apps Session and user action properties (Any mobile/custom application &amp;gt; Settings &amp;gt; Session and user action properties)&lt;/LI&gt;&lt;LI&gt;Global settings --&amp;gt; server-side service monitoring --&amp;gt; Deep monitoring&lt;UL&gt;&lt;LI&gt;has an API endpoint, but it does not cover everything on that page&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Mon, 18 Dec 2023 16:24:52 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Upgrade-to-SaaS/Settings-that-cannot-be-migrated-with-Dynatrace-Config-Manager/m-p/232262#M158</guid>
      <dc:creator>dcryans</dc:creator>
      <dc:date>2023-12-18T16:24:52Z</dc:date>
    </item>
    <item>
      <title>Re: Settings that cannot be migrated with “Dynatrace-Config-Manager”</title>
      <link>https://community.dynatrace.com/t5/Upgrade-to-SaaS/Settings-that-cannot-be-migrated-with-Dynatrace-Config-Manager/m-p/232275#M159</link>
      <description>&lt;P&gt;Honestly, if you are looking to upgrade from Managed to SaaS, I would partner directly with Dynatrace. Open a support ticket with the ask and the should be able to assist you in exporting the current settings/posture of your managed instance and then import it into your newly created SaaS instance.&amp;nbsp;&lt;/P&gt;&lt;P&gt;A cool link populated to check out as well:&amp;nbsp;&lt;A href="https://www.dynatrace.com/platform/saas-upgrade/?_ga=2.189722667.1476650388.1702901257-1341078005.1692102269&amp;amp;_gl=1%2a1ppzrqi%2a_ga%2aMTM0MTA3ODAwNS4xNjkyMTAyMjY5%2a_ga_1MEMV02JXV%2aMTcwMjkyNTQ5Mi4xOTEuMS4xNzAyOTI1NzE1LjAuMC4w" target="_blank"&gt;https://www.dynatrace.com/platform/saas-upgrade/?_ga=2.189722667.1476650388.1702901257-1341078005.1692102269&amp;amp;_gl=1%2a1ppzrqi%2a_ga%2aMTM0MTA3ODAwNS4xNjkyMTAyMjY5%2a_ga_1MEMV02JXV%2aMTcwMjkyNTQ5Mi4xOTEuMS4xNzAyOTI1NzE1LjAuMC4w&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 18 Dec 2023 18:57:04 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Upgrade-to-SaaS/Settings-that-cannot-be-migrated-with-Dynatrace-Config-Manager/m-p/232275#M159</guid>
      <dc:creator>ChadTurner</dc:creator>
      <dc:date>2023-12-18T18:57:04Z</dc:date>
    </item>
    <item>
      <title>Re: Settings that cannot be migrated with “Dynatrace-Config-Manager”</title>
      <link>https://community.dynatrace.com/t5/Upgrade-to-SaaS/Settings-that-cannot-be-migrated-with-Dynatrace-Config-Manager/m-p/236708#M173</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/32074"&gt;@Shirai&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here you can find settings that require manual migration:&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.dynatrace.com/managed/shortlink/up-migrate-cfg#settings-that-require-manual-migration" target="_blank"&gt;https://docs.dynatrace.com/managed/shortlink/up-migrate-cfg#settings-that-require-manual-migration&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyway, I think that all elements that haven´t an entity must be migrated manually.&lt;/P&gt;&lt;P&gt;I mean:&lt;/P&gt;&lt;P&gt;This element has entity:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="erh_inetum_0-1707481970709.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/17506i45EFCEF6B15464E2/image-size/medium?v=v2&amp;amp;px=400" role="button" title="erh_inetum_0-1707481970709.png" alt="erh_inetum_0-1707481970709.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="erh_inetum_1-1707482002155.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/17507i9CC5A7EF5142EB8F/image-size/medium?v=v2&amp;amp;px=400" role="button" title="erh_inetum_1-1707482002155.png" alt="erh_inetum_1-1707482002155.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;so it can migrate automatically.&lt;/P&gt;&lt;P&gt;But this one doesn´t:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="erh_inetum_2-1707482153104.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/17508iC0871C5F29A56148/image-size/medium?v=v2&amp;amp;px=400" role="button" title="erh_inetum_2-1707482153104.png" alt="erh_inetum_2-1707482153104.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;In fact, any element of Capturing section hasn´t entity associated ("..." are missing).&lt;/P&gt;&lt;P&gt;Dones anyone if I am right?&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Elena.&lt;/P&gt;</description>
      <pubDate>Fri, 09 Feb 2024 12:38:37 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Upgrade-to-SaaS/Settings-that-cannot-be-migrated-with-Dynatrace-Config-Manager/m-p/236708#M173</guid>
      <dc:creator>erh_inetum</dc:creator>
      <dc:date>2024-02-09T12:38:37Z</dc:date>
    </item>
    <item>
      <title>Re: Settings that cannot be migrated with “Dynatrace-Config-Manager”</title>
      <link>https://community.dynatrace.com/t5/Upgrade-to-SaaS/Settings-that-cannot-be-migrated-with-Dynatrace-Config-Manager/m-p/237030#M174</link>
      <description>&lt;P&gt;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/40722"&gt;@erh_inetum&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;Hi Elena,&lt;BR /&gt;&lt;BR /&gt;Be careful with that assumption, it is often right, but not always.&lt;/P&gt;&lt;P&gt;User Tags, for your example, are fully supported, see the link to the API definition&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.dynatrace.com/docs/dynatrace-api/configuration-api/rum/web-application-configuration-api/web-application/put-web-application#definition--UserTag" target="_blank"&gt;https://docs.dynatrace.com/docs/dynatrace-api/configuration-api/rum/web-application-configuration-api/web-application/put-web-application#definition--UserTag&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The ellipsis (or triple-dot) button is shown for Settings 2.0 API.&lt;/P&gt;&lt;P&gt;Applications, like in your example, are supported by API v1&lt;/P&gt;&lt;P&gt;Some Configs also use API v2&lt;BR /&gt;&lt;BR /&gt;Thank you&lt;/P&gt;</description>
      <pubDate>Tue, 13 Feb 2024 19:30:18 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Upgrade-to-SaaS/Settings-that-cannot-be-migrated-with-Dynatrace-Config-Manager/m-p/237030#M174</guid>
      <dc:creator>dcryans</dc:creator>
      <dc:date>2024-02-13T19:30:18Z</dc:date>
    </item>
    <item>
      <title>Re: Settings that cannot be migrated with “Dynatrace-Config-Manager”</title>
      <link>https://community.dynatrace.com/t5/Upgrade-to-SaaS/Settings-that-cannot-be-migrated-with-Dynatrace-Config-Manager/m-p/237426#M176</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/49327"&gt;@dcryans&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;Thanks for your clarification.&lt;/P&gt;&lt;P&gt;I'll take it into account.&lt;/P&gt;&lt;P&gt;Thanks for your help,&lt;/P&gt;&lt;P&gt;Elena.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 19 Feb 2024 13:51:30 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Upgrade-to-SaaS/Settings-that-cannot-be-migrated-with-Dynatrace-Config-Manager/m-p/237426#M176</guid>
      <dc:creator>erh_inetum</dc:creator>
      <dc:date>2024-02-19T13:51:30Z</dc:date>
    </item>
  </channel>
</rss>

