<?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: What does mean the key &amp;quot;types &amp;quot; of TimeseriesAPI? in Dynatrace API</title>
    <link>https://community.dynatrace.com/t5/Dynatrace-API/What-does-mean-the-key-quot-types-quot-of-TimeseriesAPI/m-p/118362#M878</link>
    <description>&lt;P&gt;Hi Kohei,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;To add to what Sebastian said, &lt;STRONG&gt;types &lt;/STRONG&gt;is The definition of the technology type. Used to group metrics under a logical technology name in the UI.&lt;/P&gt;&lt;P&gt;When creating custom metrics, they must be assigned a software technology type that is identical to the technology type of the custom device you are sending the metric to. For example, if you define your custom device using type &lt;STRONG&gt;F5-Firewall&lt;/STRONG&gt; you must also register all related custom metrics as type &lt;STRONG&gt;F5-Firewall&lt;/STRONG&gt;. &lt;/P&gt;&lt;P&gt;For creating custom python plugin, &lt;STRONG&gt;type &lt;/STRONG&gt;is used to describe the plugin technology, which for custom plugins is always set to &lt;STRONG&gt;python.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Hope This Helps&lt;/P&gt;&lt;P&gt;NJ&lt;/P&gt;&lt;BR /&gt;</description>
    <pubDate>Thu, 16 May 2019 12:46:48 GMT</pubDate>
    <dc:creator>nj_njoku</dc:creator>
    <dc:date>2019-05-16T12:46:48Z</dc:date>
    <item>
      <title>What does mean the key "types " of TimeseriesAPI?</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/What-does-mean-the-key-quot-types-quot-of-TimeseriesAPI/m-p/118360#M876</link>
      <description>&lt;P&gt;Hi, &lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;I believe all of timeseries metrics have "types" in the response when using TimeseriesAPI.&lt;/P&gt;&lt;P&gt;Like:&lt;/P&gt;&lt;PRE&gt;[&lt;BR /&gt;&amp;nbsp; {&lt;BR /&gt;&amp;nbsp; &amp;nbsp; "timeseriesId": "beta.python.phpfpm.dev:accepted conn",&lt;BR /&gt;&amp;nbsp; &amp;nbsp; "displayName": "accepted conn",&lt;BR /&gt;&amp;nbsp; &amp;nbsp; "dimensions":&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; [&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; "PROCESS_GROUP_INSTANCE",&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; "pool"&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; ],&lt;BR /&gt;&amp;nbsp; &amp;nbsp; "aggregationTypes":&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; [&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; "AVG",&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; "SUM",&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; "MIN",&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; "MAX"&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; ],&lt;BR /&gt;&amp;nbsp; &amp;nbsp; "unit": "Count (count)",&lt;BR /&gt;&amp;nbsp; &amp;nbsp; "filter": "PLUGIN",&lt;BR /&gt;&amp;nbsp; &amp;nbsp; "detailedSource": "PHP-FPM",&lt;BR /&gt;&amp;nbsp; &amp;nbsp; "pluginId": "beta.python.phpfpm.dev",&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &lt;STRONG&gt;&lt;EM&gt;"types": []&lt;/EM&gt;&lt;BR /&gt;&lt;/STRONG&gt;&amp;nbsp; &amp;nbsp;},&lt;BR /&gt;&amp;nbsp; &amp;nbsp;{&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;"timeseriesId": "beta.python.phpfpm.dev:active processes",&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;"displayName": "active processes",&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;"dimensions":&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; [&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; "PROCESS_GROUP_INSTANCE",&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; "pool"&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; ],&lt;BR /&gt;&amp;nbsp; &amp;nbsp; "aggregationTypes":&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; [&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; "AVG",&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; "SUM",&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; "MIN",&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; "MAX"&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; ],&lt;BR /&gt;&amp;nbsp; &amp;nbsp; "unit": "Count (count)",&lt;BR /&gt;&amp;nbsp; &amp;nbsp; "filter": "PLUGIN",&lt;BR /&gt;&amp;nbsp; &amp;nbsp; "detailedSource": "PHP-FPM",&lt;BR /&gt;&amp;nbsp; &amp;nbsp; "pluginId": "beta.python.phpfpm.dev",&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &lt;EM&gt;&lt;STRONG&gt;"types": []&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&amp;nbsp; }&lt;BR /&gt;]&lt;BR /&gt;&lt;/PRE&gt;&lt;P&gt;(&lt;A rel="noopener noreferrer" href="https://www.dynatrace.com/support/help/shortlink/api-metrics#possible-values" target="_blank"&gt;https://www.dynatrace.com/support/help/shortlink/api-metrics#possible-values&lt;/A&gt;)&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;But actually, the value of "&lt;EM&gt;&lt;STRONG&gt;types&lt;/STRONG&gt;&lt;/EM&gt;" for all metrics is empty when I checked via "&lt;EM&gt;GET list of metrics definitions&lt;/EM&gt;", then I think this is empty as default.&lt;/P&gt;&lt;P&gt;&lt;A rel="noopener noreferrer" href="https://www.dynatrace.com/support/help/shortlink/api-metrics#get-list-of-metrics-definitions-" target="_blank"&gt;https://www.dynatrace.com/support/help/shortlink/api-metrics#get-list-of-metrics-definitions-&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;So I wonder what &lt;STRONG&gt;&lt;EM&gt;"types"&lt;/EM&gt;&lt;/STRONG&gt; is for.&lt;/P&gt;&lt;P&gt;Could you tell me when this "types" should be necessary and what it is for?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Kohei Saito&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 16 May 2019 05:39:17 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/What-does-mean-the-key-quot-types-quot-of-TimeseriesAPI/m-p/118360#M876</guid>
      <dc:creator>kohei-saito</dc:creator>
      <dc:date>2019-05-16T05:39:17Z</dc:date>
    </item>
    <item>
      <title>Re: What does mean the key "types " of TimeseriesAPI?</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/What-does-mean-the-key-quot-types-quot-of-TimeseriesAPI/m-p/118361#M877</link>
      <description>&lt;P&gt;&lt;A rel="noopener noreferrer" href="https://www.dynatrace.com/support/help/extend-dynatrace/dynatrace-api/environment-api/timeseries/timeseries-api-custom-metrics/#expand-848exampleGo" target="_blank"&gt;https://www.dynatrace.com/support/help/extend-dynatrace/dynatrace-api/environment-api/timeseries/timeseries-api-custom-metrics/#expand-848example&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Go here, this is useful while you are creating custom metrics. They are the same metrics as any others in Dynatrace, this is way embedded ones has this node as well. &lt;/P&gt;&lt;P&gt;Sebastian &lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 16 May 2019 07:30:35 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/What-does-mean-the-key-quot-types-quot-of-TimeseriesAPI/m-p/118361#M877</guid>
      <dc:creator>skrystosik</dc:creator>
      <dc:date>2019-05-16T07:30:35Z</dc:date>
    </item>
    <item>
      <title>Re: What does mean the key "types " of TimeseriesAPI?</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/What-does-mean-the-key-quot-types-quot-of-TimeseriesAPI/m-p/118362#M878</link>
      <description>&lt;P&gt;Hi Kohei,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;To add to what Sebastian said, &lt;STRONG&gt;types &lt;/STRONG&gt;is The definition of the technology type. Used to group metrics under a logical technology name in the UI.&lt;/P&gt;&lt;P&gt;When creating custom metrics, they must be assigned a software technology type that is identical to the technology type of the custom device you are sending the metric to. For example, if you define your custom device using type &lt;STRONG&gt;F5-Firewall&lt;/STRONG&gt; you must also register all related custom metrics as type &lt;STRONG&gt;F5-Firewall&lt;/STRONG&gt;. &lt;/P&gt;&lt;P&gt;For creating custom python plugin, &lt;STRONG&gt;type &lt;/STRONG&gt;is used to describe the plugin technology, which for custom plugins is always set to &lt;STRONG&gt;python.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Hope This Helps&lt;/P&gt;&lt;P&gt;NJ&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 16 May 2019 12:46:48 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/What-does-mean-the-key-quot-types-quot-of-TimeseriesAPI/m-p/118362#M878</guid>
      <dc:creator>nj_njoku</dc:creator>
      <dc:date>2019-05-16T12:46:48Z</dc:date>
    </item>
    <item>
      <title>Re: What does mean the key "types " of TimeseriesAPI?</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/What-does-mean-the-key-quot-types-quot-of-TimeseriesAPI/m-p/118363#M879</link>
      <description>&lt;P&gt;Hi Sebastian and Ugochukwu,&lt;/P&gt;&lt;P&gt;Thank you for answers.&lt;/P&gt;&lt;P&gt;I understand that "&lt;STRONG&gt;&lt;EM&gt;types&lt;/EM&gt;&lt;/STRONG&gt;" is useful for the definition of  a logical technology name only in the creation of custom metric, so there are no values of "types" for the default metrics.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Is it shown in the &lt;EM&gt;&lt;STRONG&gt;"Techonologies"&lt;/STRONG&gt;&lt;/EM&gt; view?&lt;BR /&gt;(I think so)&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Kohei &lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 17 May 2019 08:24:22 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/What-does-mean-the-key-quot-types-quot-of-TimeseriesAPI/m-p/118363#M879</guid>
      <dc:creator>kohei-saito</dc:creator>
      <dc:date>2019-05-17T08:24:22Z</dc:date>
    </item>
  </channel>
</rss>

