<?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 Correlating multiple disk entities within host entity using Metrics API in Dynatrace API</title>
    <link>https://community.dynatrace.com/t5/Dynatrace-API/Correlating-multiple-disk-entities-within-host-entity-using/m-p/123501#M1050</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;I have a set of python scripts used for extract of timeseries metrics using Metrics API v2. Reason is to repetitively extract detailed statistics for long term capacity planning - to avoid the issue that eventually, when the data is needed for planning - dynatrace would have long summarised it in hourly or daily averages. Yep - capacity planners do like to have access to piles of data (different discussion).&lt;/P&gt;
&lt;P&gt;Staying on topic... I am unable to figure out how to correlate multiple attached entities to host entity. For example in human readable form host is usually a hostName not entitiyId that looks like 'HOST-XXXXXXXXX'. That host usually has multiple disks attached, each with its own metrics:&lt;/P&gt;
&lt;P&gt;so:&lt;/P&gt;
&lt;PRE&gt;HOST-1234567 (myhost.com): DISK-12345 (C:\), DISK-12346 (F:\)&lt;/PRE&gt;
&lt;P&gt;I am unable to create the relationship that allows me to extract disk utilisation data for:&lt;/P&gt;
&lt;PRE&gt;myhost.com/disk-c:&lt;BR /&gt;myhost.com/disk-f:&lt;/PRE&gt;
&lt;P&gt;My process is to - find a host from the list of all host entities by matching hostName from the resulting list of hosts entities.&lt;/P&gt;
&lt;P&gt;I can then use this entity to extract CPU/MEMORY time series data - that is fine&lt;/P&gt;
&lt;P&gt;BUT, I can't find the way of extracting DISK utilisation for a particular disk. Interestingly, the Metrics v2 API returns this:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;"metrics": {&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; "builtin:host.disk.used": {&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; "series": [&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; {&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; "dimensions": [&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &lt;STRONG&gt;"HOST-9483C7D89472AF43"&lt;/STRONG&gt;,&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &lt;STRONG&gt;"DISK-51D7D5BE9D2A1FE2"&lt;/STRONG&gt;&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; ],&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; "values": [&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; {&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; "timestamp": 1568095200000,&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; "value": 5.170616996598518E10&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; },&lt;BR /&gt;ETC...&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I can't, for the life of me, find what the "&lt;STRONG&gt;DISK-51D7D5BE9D2A1FE2&lt;/STRONG&gt;" actually is - is it a C:\ or F:\ drive? There seem to be no way of correlating these or even finding out the 'human readable' description/name of the entity/device. The devices are not listed in the host entity detailed information.&lt;/P&gt;
&lt;P&gt;Anyone can point me in the direction of how the configuration (host:disk[X] or host:cpu[x] or host:netinterface[X]) works? Docs? Tutorials? Any API architects? Any E-R diagrams of how the structure is supposed to look like? Any Dynatrace API libraries usable by python that allow something like 'getDiskByHostName(host)' lol ?&lt;/P&gt;
&lt;P&gt;Thanks for reading this...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 03 Oct 2022 10:07:27 GMT</pubDate>
    <dc:creator>snikolic</dc:creator>
    <dc:date>2022-10-03T10:07:27Z</dc:date>
    <item>
      <title>Correlating multiple disk entities within host entity using Metrics API</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/Correlating-multiple-disk-entities-within-host-entity-using/m-p/123501#M1050</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;I have a set of python scripts used for extract of timeseries metrics using Metrics API v2. Reason is to repetitively extract detailed statistics for long term capacity planning - to avoid the issue that eventually, when the data is needed for planning - dynatrace would have long summarised it in hourly or daily averages. Yep - capacity planners do like to have access to piles of data (different discussion).&lt;/P&gt;
&lt;P&gt;Staying on topic... I am unable to figure out how to correlate multiple attached entities to host entity. For example in human readable form host is usually a hostName not entitiyId that looks like 'HOST-XXXXXXXXX'. That host usually has multiple disks attached, each with its own metrics:&lt;/P&gt;
&lt;P&gt;so:&lt;/P&gt;
&lt;PRE&gt;HOST-1234567 (myhost.com): DISK-12345 (C:\), DISK-12346 (F:\)&lt;/PRE&gt;
&lt;P&gt;I am unable to create the relationship that allows me to extract disk utilisation data for:&lt;/P&gt;
&lt;PRE&gt;myhost.com/disk-c:&lt;BR /&gt;myhost.com/disk-f:&lt;/PRE&gt;
&lt;P&gt;My process is to - find a host from the list of all host entities by matching hostName from the resulting list of hosts entities.&lt;/P&gt;
&lt;P&gt;I can then use this entity to extract CPU/MEMORY time series data - that is fine&lt;/P&gt;
&lt;P&gt;BUT, I can't find the way of extracting DISK utilisation for a particular disk. Interestingly, the Metrics v2 API returns this:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;"metrics": {&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; "builtin:host.disk.used": {&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; "series": [&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; {&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; "dimensions": [&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &lt;STRONG&gt;"HOST-9483C7D89472AF43"&lt;/STRONG&gt;,&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &lt;STRONG&gt;"DISK-51D7D5BE9D2A1FE2"&lt;/STRONG&gt;&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; ],&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; "values": [&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; {&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; "timestamp": 1568095200000,&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; "value": 5.170616996598518E10&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; },&lt;BR /&gt;ETC...&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I can't, for the life of me, find what the "&lt;STRONG&gt;DISK-51D7D5BE9D2A1FE2&lt;/STRONG&gt;" actually is - is it a C:\ or F:\ drive? There seem to be no way of correlating these or even finding out the 'human readable' description/name of the entity/device. The devices are not listed in the host entity detailed information.&lt;/P&gt;
&lt;P&gt;Anyone can point me in the direction of how the configuration (host:disk[X] or host:cpu[x] or host:netinterface[X]) works? Docs? Tutorials? Any API architects? Any E-R diagrams of how the structure is supposed to look like? Any Dynatrace API libraries usable by python that allow something like 'getDiskByHostName(host)' lol ?&lt;/P&gt;
&lt;P&gt;Thanks for reading this...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 03 Oct 2022 10:07:27 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/Correlating-multiple-disk-entities-within-host-entity-using/m-p/123501#M1050</guid>
      <dc:creator>snikolic</dc:creator>
      <dc:date>2022-10-03T10:07:27Z</dc:date>
    </item>
    <item>
      <title>Re: Correlating multiple disk entities within host entity using Metrics API</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/Correlating-multiple-disk-entities-within-host-entity-using/m-p/123502#M1051</link>
      <description>&lt;P&gt;For now the only way I've found is checking dynatrace page source on disk dashboard:&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.dynatrace.com/legacyfs/online/21984-1569306778241.png" /&gt;&lt;/P&gt;&lt;P&gt;debugid is what you need... You're right I don't see and API endpoint that is able to resolve it. &lt;/P&gt;&lt;P&gt;Sebastian &lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 24 Sep 2019 06:33:36 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/Correlating-multiple-disk-entities-within-host-entity-using/m-p/123502#M1051</guid>
      <dc:creator>skrystosik</dc:creator>
      <dc:date>2019-09-24T06:33:36Z</dc:date>
    </item>
    <item>
      <title>Re: Correlating multiple disk entities within host entity using Metrics API</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/Correlating-multiple-disk-entities-within-host-entity-using/m-p/123503#M1052</link>
      <description>&lt;P&gt;Thanks &lt;A rel="user" href="https://answers.dynatrace.com/users/15061/view.html" nodeid="15061"&gt;@sebastian k.&lt;/A&gt;, good point. It is a bit of a workaround, as I need to fish out the disk entity Id's manually and add them to my configuration list, but solution is good enough for now, until the API matures.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 24 Sep 2019 23:04:02 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/Correlating-multiple-disk-entities-within-host-entity-using/m-p/123503#M1052</guid>
      <dc:creator>snikolic</dc:creator>
      <dc:date>2019-09-24T23:04:02Z</dc:date>
    </item>
    <item>
      <title>Re: Correlating multiple disk entities within host entity using Metrics API</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/Correlating-multiple-disk-entities-within-host-entity-using/m-p/123504#M1053</link>
      <description>&lt;P&gt;Happy to hear that I've helped &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; &lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 25 Sep 2019 07:56:33 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/Correlating-multiple-disk-entities-within-host-entity-using/m-p/123504#M1053</guid>
      <dc:creator>skrystosik</dc:creator>
      <dc:date>2019-09-25T07:56:33Z</dc:date>
    </item>
    <item>
      <title>Re: Correlating multiple disk entities within host entity using Metrics API</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/Correlating-multiple-disk-entities-within-host-entity-using/m-p/168627#M1327</link>
      <description>&lt;P&gt;Hey guys, any update on this since then? Nowadays are we able to retrieve the disk name using any API?&lt;/P&gt;</description>
      <pubDate>Thu, 01 Jul 2021 20:37:15 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/Correlating-multiple-disk-entities-within-host-entity-using/m-p/168627#M1327</guid>
      <dc:creator>AlexandreFranca</dc:creator>
      <dc:date>2021-07-01T20:37:15Z</dc:date>
    </item>
  </channel>
</rss>

