<?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 VMWare Tags into Dynatrace and the VMWare Remote Extension questions in Extensions</title>
    <link>https://community.dynatrace.com/t5/Extensions/VMWare-Tags-into-Dynatrace-and-the-VMWare-Remote-Extension/m-p/277581#M6460</link>
    <description>&lt;P&gt;We would like to get VMWare tags into Dynatrace.&amp;nbsp; Now, I understand this is a feature of the VMWare Remote Extension monitor (among other things), but I also don't understand what the point of that extension is other than that.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It seems to bring in a lot of the same metrics that the out-of-the-box extension does plus more.&amp;nbsp; So, my question is, why would Dynatrace not just add these features to the out-of-the-box integration?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I also would like to know if there are any other options for getting VMWare tags about VM's into Dynatrace and associated with the hosts besides using that extension?&lt;/P&gt;</description>
    <pubDate>Wed, 21 May 2025 06:21:42 GMT</pubDate>
    <dc:creator>36Krazyfists</dc:creator>
    <dc:date>2025-05-21T06:21:42Z</dc:date>
    <item>
      <title>VMWare Tags into Dynatrace and the VMWare Remote Extension questions</title>
      <link>https://community.dynatrace.com/t5/Extensions/VMWare-Tags-into-Dynatrace-and-the-VMWare-Remote-Extension/m-p/277581#M6460</link>
      <description>&lt;P&gt;We would like to get VMWare tags into Dynatrace.&amp;nbsp; Now, I understand this is a feature of the VMWare Remote Extension monitor (among other things), but I also don't understand what the point of that extension is other than that.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It seems to bring in a lot of the same metrics that the out-of-the-box extension does plus more.&amp;nbsp; So, my question is, why would Dynatrace not just add these features to the out-of-the-box integration?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I also would like to know if there are any other options for getting VMWare tags about VM's into Dynatrace and associated with the hosts besides using that extension?&lt;/P&gt;</description>
      <pubDate>Wed, 21 May 2025 06:21:42 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Extensions/VMWare-Tags-into-Dynatrace-and-the-VMWare-Remote-Extension/m-p/277581#M6460</guid>
      <dc:creator>36Krazyfists</dc:creator>
      <dc:date>2025-05-21T06:21:42Z</dc:date>
    </item>
    <item>
      <title>Re: VMWare Tags into Dynatrace and the VMWare Remote Extension questions</title>
      <link>https://community.dynatrace.com/t5/Extensions/VMWare-Tags-into-Dynatrace-and-the-VMWare-Remote-Extension/m-p/289636#M6852</link>
      <description>&lt;P&gt;I have the same question, and I’m facing a similar situation in our environment. At the moment, both the VMware extension and the native vSphere connection are active simultaneously, which results in potential duplicate metrics. So to control consumption and cost, I’ve had to manually disable overlapping metrics within the extension. It would be far cleaner - and more efficient—to rely on a single data source instead of running both in parallel.&lt;/P&gt;&lt;P&gt;Additionally, Azure can pass through tags automatically when connected via a service principal. I’m hoping Dynatrace can support the same kind of tag passthrough capability, as this would make governance, management zones, and cost attribution far easier to maintain.&lt;/P&gt;</description>
      <pubDate>Sat, 15 Nov 2025 17:01:29 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Extensions/VMWare-Tags-into-Dynatrace-and-the-VMWare-Remote-Extension/m-p/289636#M6852</guid>
      <dc:creator>ChrisRFonz</dc:creator>
      <dc:date>2025-11-15T17:01:29Z</dc:date>
    </item>
  </channel>
</rss>

