<?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: More than one TimeseriesId in One call on one host in the TimeSeries API in Dynatrace API</title>
    <link>https://community.dynatrace.com/t5/Dynatrace-API/More-than-one-TimeseriesId-in-One-call-on-one-host-in-the/m-p/28678#M2297</link>
    <description>&lt;P&gt;Sorry just one metric at a time but for multiple entities. Requesting all metrics for all entities with one call would definitely introduce an issue in large environments with 10K+ hosts.&lt;/P&gt;</description>
    <pubDate>Tue, 27 Jun 2017 13:26:13 GMT</pubDate>
    <dc:creator>wolfgang_beer</dc:creator>
    <dc:date>2017-06-27T13:26:13Z</dc:date>
    <item>
      <title>More than one TimeseriesId in One call on one host in the TimeSeries API</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/More-than-one-TimeseriesId-in-One-call-on-one-host-in-the/m-p/28677#M2296</link>
      <description>&lt;P&gt;Can you get more than one or all of the timeseries for one host in one call of the TimeSeries REST Interface.&lt;/P&gt;
&lt;P&gt;So maybe curl ‐L ‐H "Authorization: Api‐Token {token} \ "https://{id}.live.dynatrace.com/api/v1/timeseries?relativeTime=hour&amp;amp;entity=HOST‐B64B6B9CB11E2244&amp;amp;aggregationType=AVG&amp;amp;timeseriesId=*"&lt;/P&gt;</description>
      <pubDate>Mon, 13 Feb 2023 20:46:47 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/More-than-one-TimeseriesId-in-One-call-on-one-host-in-the/m-p/28677#M2296</guid>
      <dc:creator>rb0c70091</dc:creator>
      <dc:date>2023-02-13T20:46:47Z</dc:date>
    </item>
    <item>
      <title>Re: More than one TimeseriesId in One call on one host in the TimeSeries API</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/More-than-one-TimeseriesId-in-One-call-on-one-host-in-the/m-p/28678#M2297</link>
      <description>&lt;P&gt;Sorry just one metric at a time but for multiple entities. Requesting all metrics for all entities with one call would definitely introduce an issue in large environments with 10K+ hosts.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Jun 2017 13:26:13 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/More-than-one-TimeseriesId-in-One-call-on-one-host-in-the/m-p/28678#M2297</guid>
      <dc:creator>wolfgang_beer</dc:creator>
      <dc:date>2017-06-27T13:26:13Z</dc:date>
    </item>
  </channel>
</rss>

