<?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: Smartscape limitation in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/Smartscape-limitation/m-p/239084#M31394</link>
    <description>&lt;P&gt;I would suggest to you to submit these improvements as an idea in the community. Then members can up-vote it if they find these improvements relevant as well and it will be brought to the attention of Dynatrace developers.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Maybe start with the global timeframe selector which could be applied to the Smartscape? I can imagine that this will consume a lot of resources when you want to consider 1 week + (so maybe this is the reason why it does not exist) but maybe Dynatrace can reply to your idea to justify the chosen timeframe or explain if they're currently busy with expanding it.&lt;/P&gt;</description>
    <pubDate>Wed, 06 Mar 2024 11:25:24 GMT</pubDate>
    <dc:creator>marina_pollehn</dc:creator>
    <dc:date>2024-03-06T11:25:24Z</dc:date>
    <item>
      <title>Smartscape limitation</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Smartscape-limitation/m-p/238267#M31288</link>
      <description>&lt;P&gt;1. Cannot apply time filter&lt;/P&gt;
&lt;P&gt;2. Doesn't correlate horizontally. ie service to service or process to process. That is time based behavior correlation.&lt;/P&gt;
&lt;P&gt;3. Vertical correlation is low value. ie service to process to host is easy to determine even without smartscape&lt;/P&gt;
&lt;P&gt;Let me know if I missed something.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Feb 2024 07:40:12 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Smartscape-limitation/m-p/238267#M31288</guid>
      <dc:creator>vchandna</dc:creator>
      <dc:date>2024-02-28T07:40:12Z</dc:date>
    </item>
    <item>
      <title>Re: Smartscape limitation</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Smartscape-limitation/m-p/239084#M31394</link>
      <description>&lt;P&gt;I would suggest to you to submit these improvements as an idea in the community. Then members can up-vote it if they find these improvements relevant as well and it will be brought to the attention of Dynatrace developers.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Maybe start with the global timeframe selector which could be applied to the Smartscape? I can imagine that this will consume a lot of resources when you want to consider 1 week + (so maybe this is the reason why it does not exist) but maybe Dynatrace can reply to your idea to justify the chosen timeframe or explain if they're currently busy with expanding it.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 11:25:24 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Smartscape-limitation/m-p/239084#M31394</guid>
      <dc:creator>marina_pollehn</dc:creator>
      <dc:date>2024-03-06T11:25:24Z</dc:date>
    </item>
  </channel>
</rss>

