<?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 vCenter integration gaps, datastore latency not correlating with VM-level performance in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/vCenter-integration-gaps-datastore-latency-not-correlating-with/m-p/302395#M39310</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;For VMware environments monitored through the vCenter integration, are you supplementing the native infrastructure metrics with any additional monitoring or extensions (for example, storage-level metrics, NSX/network visibility, vSwitch metrics, or guest OS-level processes not surfaced through vCenter)?&lt;/P&gt;&lt;P&gt;We're currently relying on the native vCenter integration, but we've noticed that datastore latency spikes don't always correlate cleanly with what we see at the VM level. In some cases, by the time a performance issue becomes visible within the guest OS, the underlying storage bottleneck has already passed, making post-incident root cause analysis more challenging.&lt;/P&gt;&lt;P&gt;I'm interested to hear what gaps others have encountered when relying solely on vCenter monitoring, particularly around:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Datastore/storage latency visibility&lt;/LI&gt;&lt;LI&gt;NSX and network path visibility&lt;/LI&gt;&lt;LI&gt;Correlating infrastructure issues with VM or application impact&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Have you implemented any additional Dynatrace extensions, integrations, or monitoring approaches to address these gaps?&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Sujit&lt;/P&gt;&lt;/DIV&gt;</description>
    <pubDate>Sat, 25 Jul 2026 00:02:18 GMT</pubDate>
    <dc:creator>sujit_k_singh</dc:creator>
    <dc:date>2026-07-25T00:02:18Z</dc:date>
    <item>
      <title>vCenter integration gaps, datastore latency not correlating with VM-level performance</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/vCenter-integration-gaps-datastore-latency-not-correlating-with/m-p/302395#M39310</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;For VMware environments monitored through the vCenter integration, are you supplementing the native infrastructure metrics with any additional monitoring or extensions (for example, storage-level metrics, NSX/network visibility, vSwitch metrics, or guest OS-level processes not surfaced through vCenter)?&lt;/P&gt;&lt;P&gt;We're currently relying on the native vCenter integration, but we've noticed that datastore latency spikes don't always correlate cleanly with what we see at the VM level. In some cases, by the time a performance issue becomes visible within the guest OS, the underlying storage bottleneck has already passed, making post-incident root cause analysis more challenging.&lt;/P&gt;&lt;P&gt;I'm interested to hear what gaps others have encountered when relying solely on vCenter monitoring, particularly around:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Datastore/storage latency visibility&lt;/LI&gt;&lt;LI&gt;NSX and network path visibility&lt;/LI&gt;&lt;LI&gt;Correlating infrastructure issues with VM or application impact&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Have you implemented any additional Dynatrace extensions, integrations, or monitoring approaches to address these gaps?&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Sujit&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Sat, 25 Jul 2026 00:02:18 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/vCenter-integration-gaps-datastore-latency-not-correlating-with/m-p/302395#M39310</guid>
      <dc:creator>sujit_k_singh</dc:creator>
      <dc:date>2026-07-25T00:02:18Z</dc:date>
    </item>
  </channel>
</rss>

