<?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 Trend of documentation missing key information in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/Trend-of-documentation-missing-key-information/m-p/274669#M36259</link>
    <description>&lt;P&gt;I hate complaining as I strongly believe in Dynatrace's product and the support however as someone who works daily within the product I'm noticing more and more the documentation around the implementation of extensions and new functionality can be opportunistic at best.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'll provide several examples below where key information isn't readily apparent.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;SAML Configuration&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.dynatrace.com/docs/manage/identity-access-management/user-and-group-management/access-saml#verify-ownership" target="_blank"&gt;https://docs.dynatrace.com/docs/manage/identity-access-management/user-and-group-management/access-saml#verify-ownership&lt;/A&gt;&lt;/P&gt;&lt;P&gt;For SAML Configuration, it doesn't provide a clear path to convert from one IdP to another. Nor does it provide clear expectations around failbacks or things to avoid. For example, once you've verified your domain and have a legacy configuration in place, you cannot just disable the current configuration and build a new one, the GUI will not let you.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Another example would be the Redis 2.0 extension in the Hub&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.dynatrace.com/docs/ingest-from/technology-support/dynatrace-extensions/supported-out-of-the-box/redis" target="_blank"&gt;https://docs.dynatrace.com/docs/ingest-from/technology-support/dynatrace-extensions/supported-out-of-the-box/redis&lt;/A&gt;&lt;/P&gt;&lt;P&gt;The documentation doesn't give examples of valid configurations nor does it provide any key details around authentication requirements or troubleshooting. This seems to be a trend overall in the hub, and the new GUI makes you have to go to multiple places to even be able to see the logs presented once an extension is enabled.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 08 Apr 2025 13:13:01 GMT</pubDate>
    <dc:creator>john_martin</dc:creator>
    <dc:date>2025-04-08T13:13:01Z</dc:date>
    <item>
      <title>Trend of documentation missing key information</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Trend-of-documentation-missing-key-information/m-p/274669#M36259</link>
      <description>&lt;P&gt;I hate complaining as I strongly believe in Dynatrace's product and the support however as someone who works daily within the product I'm noticing more and more the documentation around the implementation of extensions and new functionality can be opportunistic at best.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'll provide several examples below where key information isn't readily apparent.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;SAML Configuration&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.dynatrace.com/docs/manage/identity-access-management/user-and-group-management/access-saml#verify-ownership" target="_blank"&gt;https://docs.dynatrace.com/docs/manage/identity-access-management/user-and-group-management/access-saml#verify-ownership&lt;/A&gt;&lt;/P&gt;&lt;P&gt;For SAML Configuration, it doesn't provide a clear path to convert from one IdP to another. Nor does it provide clear expectations around failbacks or things to avoid. For example, once you've verified your domain and have a legacy configuration in place, you cannot just disable the current configuration and build a new one, the GUI will not let you.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Another example would be the Redis 2.0 extension in the Hub&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.dynatrace.com/docs/ingest-from/technology-support/dynatrace-extensions/supported-out-of-the-box/redis" target="_blank"&gt;https://docs.dynatrace.com/docs/ingest-from/technology-support/dynatrace-extensions/supported-out-of-the-box/redis&lt;/A&gt;&lt;/P&gt;&lt;P&gt;The documentation doesn't give examples of valid configurations nor does it provide any key details around authentication requirements or troubleshooting. This seems to be a trend overall in the hub, and the new GUI makes you have to go to multiple places to even be able to see the logs presented once an extension is enabled.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 08 Apr 2025 13:13:01 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Trend-of-documentation-missing-key-information/m-p/274669#M36259</guid>
      <dc:creator>john_martin</dc:creator>
      <dc:date>2025-04-08T13:13:01Z</dc:date>
    </item>
  </channel>
</rss>

