<?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: How to optimize querying the Dynatrace API to retrieve information about process group instances in Dynatrace API</title>
    <link>https://community.dynatrace.com/t5/Dynatrace-API/How-to-optimize-querying-the-Dynatrace-API-to-retrieve/m-p/248871#M3208</link>
    <description>&lt;P&gt;I understand you want to make the query faster, was wondering what is the reason you need to export all the PGIs &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;As you noticed the number PGIs is quite huge so I would suggest reducing the fields to the necessary ones, and maybe extract more for specific entities afterwards.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 21 Jun 2024 12:37:05 GMT</pubDate>
    <dc:creator>mark_bley</dc:creator>
    <dc:date>2024-06-21T12:37:05Z</dc:date>
    <item>
      <title>How to optimize querying the Dynatrace API to retrieve information about process group instances?</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/How-to-optimize-querying-the-Dynatrace-API-to-retrieve/m-p/248803#M3203</link>
      <description>&lt;P&gt;I am retrieving process group instances using this kind of query: "/v2/entities?entitySelector=type(process_group_instance)&amp;amp;fields=toRelationships,fromRelationships,properties.metadata,properties.softwareTechnologies";&lt;/P&gt;
&lt;P&gt;I am concerned that number of instances it returns is relatively large.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Would be removal of Relationships help with response size? Are the Relationships mandatory to retrieve process group instances? If Relationships can not be removed then what would be query optimization suggestions?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 08 Aug 2024 13:52:24 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/How-to-optimize-querying-the-Dynatrace-API-to-retrieve/m-p/248803#M3203</guid>
      <dc:creator>mrpoppler</dc:creator>
      <dc:date>2024-08-08T13:52:24Z</dc:date>
    </item>
    <item>
      <title>Re: How to optimize querying the Dynatrace API to retrieve information about process group instances</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/How-to-optimize-querying-the-Dynatrace-API-to-retrieve/m-p/248805#M3204</link>
      <description>&lt;P&gt;What is the goal ?&lt;/P&gt;&lt;P&gt;You can just pull pgis with&amp;nbsp;&lt;SPAN&gt;entitySelector=type(process_group_instance) as parameter fields is optional.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;If you want specific pgis extend the entitySelector with e.g. relationship to a Host, Host group, service, application...&lt;/SPAN&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;type(PROCESS_GROUP_INSTANCE),fromRelationships.isProcessOf(type("HOST"),entityName("foo"))&lt;/LI-CODE&gt;&lt;P&gt;Many possibilities...&lt;/P&gt;</description>
      <pubDate>Thu, 20 Jun 2024 17:32:42 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/How-to-optimize-querying-the-Dynatrace-API-to-retrieve/m-p/248805#M3204</guid>
      <dc:creator>mark_bley</dc:creator>
      <dc:date>2024-06-20T17:32:42Z</dc:date>
    </item>
    <item>
      <title>Re: How to optimize querying the Dynatrace API to retrieve information about process group instances</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/How-to-optimize-querying-the-Dynatrace-API-to-retrieve/m-p/248810#M3206</link>
      <description>&lt;P&gt;The goal is to make the query faster.&amp;nbsp; So that result of the query becomes shorter yet it should be sufficient to retrieve entities like business applications. And idea is to remove toRelationships and fromRelationships for that from the query.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 20 Jun 2024 20:39:57 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/How-to-optimize-querying-the-Dynatrace-API-to-retrieve/m-p/248810#M3206</guid>
      <dc:creator>mrpoppler</dc:creator>
      <dc:date>2024-06-20T20:39:57Z</dc:date>
    </item>
    <item>
      <title>Re: How to optimize querying the Dynatrace API to retrieve information about process group instances</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/How-to-optimize-querying-the-Dynatrace-API-to-retrieve/m-p/248825#M3207</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;BR /&gt;&amp;nbsp;You can use the fields value to reduce what you pull down and or select&lt;BR /&gt;&lt;A href="https://docs.dynatrace.com/docs/dynatrace-api/environment-api/entity-v2/get-entity-type#response-body-objects" target="_blank" rel="noopener"&gt;Monitored entities API - GET entity type - Dynatrace Docs&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Example below :&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="python"&gt;params = {
    "entitySelector": 'type("Process_Group")',
    "fields": "properties.softwareTechnologies,fromRelationships,toRelationships,properties,tags",
    "Api-Token": "dt0c01."
}&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this helps&lt;/P&gt;</description>
      <pubDate>Fri, 21 Jun 2024 04:39:07 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/How-to-optimize-querying-the-Dynatrace-API-to-retrieve/m-p/248825#M3207</guid>
      <dc:creator>gopher</dc:creator>
      <dc:date>2024-06-21T04:39:07Z</dc:date>
    </item>
    <item>
      <title>Re: How to optimize querying the Dynatrace API to retrieve information about process group instances</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/How-to-optimize-querying-the-Dynatrace-API-to-retrieve/m-p/248871#M3208</link>
      <description>&lt;P&gt;I understand you want to make the query faster, was wondering what is the reason you need to export all the PGIs &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;As you noticed the number PGIs is quite huge so I would suggest reducing the fields to the necessary ones, and maybe extract more for specific entities afterwards.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Jun 2024 12:37:05 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/How-to-optimize-querying-the-Dynatrace-API-to-retrieve/m-p/248871#M3208</guid>
      <dc:creator>mark_bley</dc:creator>
      <dc:date>2024-06-21T12:37:05Z</dc:date>
    </item>
    <item>
      <title>Re: How to optimize querying the Dynatrace API to retrieve information about process group instances</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/How-to-optimize-querying-the-Dynatrace-API-to-retrieve/m-p/248904#M3212</link>
      <description>&lt;P&gt;Agreed, first of all, use &lt;A href="https://docs.dynatrace.com/docs/shortlink/api-entities-v2-selector" target="_self"&gt;&lt;STRONG&gt;entitySelector&lt;/STRONG&gt;&lt;/A&gt; to query only process group instances you are interested in. (using management zone, process group properties, etc). Secondly select just fields you need.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Jun 2024 20:10:48 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/How-to-optimize-querying-the-Dynatrace-API-to-retrieve/m-p/248904#M3212</guid>
      <dc:creator>Julius_Loman</dc:creator>
      <dc:date>2024-06-21T20:10:48Z</dc:date>
    </item>
  </channel>
</rss>

