<?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>question Re: What does entityName mean in CM API response? in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/What-does-entityName-mean-in-CM-API-response/m-p/412457#M253460</link>
    <description>&lt;P&gt;Hi,&amp;nbsp;Snm1523&lt;BR /&gt;&lt;BR /&gt;hdfs:&amp;lt;nameservice&amp;gt;, is available when HA is enabled on HDFS (HDFS &amp;gt; Configuration tab &amp;gt;&amp;nbsp;NameNode Nameservice)&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://docs.cloudera.com/cdp-private-cloud-base/7.1.9/fault-tolerance/topics/cr-enabling-high-availability-and-automatic-failover.html" target="_blank"&gt;https://docs.cloudera.com/cdp-private-cloud-base/7.1.9/fault-tolerance/topics/cr-enabling-high-availability-and-automatic-failover.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;You can just show one, editing the query and adding "and entityName='hdfs'" or "and entityName='hdfs:&amp;lt;nameservice&amp;gt;'"&lt;BR /&gt;&lt;BR /&gt;For instance,&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;select total_bytes_read_rate_across_datanodes, total_bytes_written_rate_across_datanodes where category = SERVICE and serviceType = HDFS and entityName = 'hdfs'&lt;BR /&gt;&lt;BR /&gt;Hope it helps.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Christian.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 24 Sep 2025 20:07:36 GMT</pubDate>
    <dc:creator>cdebernardi</dc:creator>
    <dc:date>2025-09-24T20:07:36Z</dc:date>
    <item>
      <title>What does entityName mean in CM API response?</title>
      <link>https://community.cloudera.com/t5/Support-Questions/What-does-entityName-mean-in-CM-API-response/m-p/412311#M253367</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I have noticed in one of the charts (HDFS IO) available in CM dashboard for HDFS that runs below query have got values pulled from 2 separate entities for the same metric. Attached are the 3 screenshots for reference. 2 graphs showing values from individual entities and 1 the combined graph available in CM that triggers below query.&lt;/P&gt;&lt;P&gt;&lt;EM&gt;select total_bytes_read_rate_across_datanodes, total_bytes_written_rate_across_datanodes where category = SERVICE and serviceType = HDFS and clusterId = "1"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;Two different entities are &lt;STRONG&gt;hdfs&lt;/STRONG&gt; and &lt;STRONG&gt;hdfs:&amp;lt;cluster_name&amp;gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;I have also verified the response from below API call, and it does returns both entities and both have latest data.&lt;/P&gt;&lt;P&gt;http://&amp;lt;cm-host&amp;gt;:7180/api/v19/timeseries?query=SELECT%20total_bytes_written_rate_across_datanodes%20WHERE%20category=SERVICE&lt;/P&gt;&lt;P&gt;What do they mean?&lt;BR /&gt;Where are they coming from?&lt;BR /&gt;How to get it fixed so a single value is returned for the metric?&lt;/P&gt;&lt;P&gt;Kindly advise.&lt;/P&gt;&lt;P&gt;Thanks&lt;BR /&gt;Snm1523&lt;/P&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="image (6).png" style="width: 999px;"&gt;&lt;img src="https://community.cloudera.com/t5/image/serverpage/image-id/46311i6235978DCD63BDB1/image-size/large?v=v2&amp;amp;px=999" role="button" title="image (6).png" alt="image (6).png" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="image (5).png" style="width: 999px;"&gt;&lt;img src="https://community.cloudera.com/t5/image/serverpage/image-id/46312iC73BA2B5FFBA8147/image-size/large?v=v2&amp;amp;px=999" role="button" title="image (5).png" alt="image (5).png" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Screenshot 2025-09-09 at 11.36.15.png" style="width: 999px;"&gt;&lt;img src="https://community.cloudera.com/t5/image/serverpage/image-id/46313i4913F0B18060F5A6/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screenshot 2025-09-09 at 11.36.15.png" alt="Screenshot 2025-09-09 at 11.36.15.png" /&gt;&lt;/span&gt;</description>
      <pubDate>Tue, 21 Apr 2026 06:17:06 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/What-does-entityName-mean-in-CM-API-response/m-p/412311#M253367</guid>
      <dc:creator>snm1523</dc:creator>
      <dc:date>2026-04-21T06:17:06Z</dc:date>
    </item>
    <item>
      <title>Re: What does entityName mean in CM API response?</title>
      <link>https://community.cloudera.com/t5/Support-Questions/What-does-entityName-mean-in-CM-API-response/m-p/412457#M253460</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;Snm1523&lt;BR /&gt;&lt;BR /&gt;hdfs:&amp;lt;nameservice&amp;gt;, is available when HA is enabled on HDFS (HDFS &amp;gt; Configuration tab &amp;gt;&amp;nbsp;NameNode Nameservice)&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://docs.cloudera.com/cdp-private-cloud-base/7.1.9/fault-tolerance/topics/cr-enabling-high-availability-and-automatic-failover.html" target="_blank"&gt;https://docs.cloudera.com/cdp-private-cloud-base/7.1.9/fault-tolerance/topics/cr-enabling-high-availability-and-automatic-failover.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;You can just show one, editing the query and adding "and entityName='hdfs'" or "and entityName='hdfs:&amp;lt;nameservice&amp;gt;'"&lt;BR /&gt;&lt;BR /&gt;For instance,&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;select total_bytes_read_rate_across_datanodes, total_bytes_written_rate_across_datanodes where category = SERVICE and serviceType = HDFS and entityName = 'hdfs'&lt;BR /&gt;&lt;BR /&gt;Hope it helps.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Christian.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 24 Sep 2025 20:07:36 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/What-does-entityName-mean-in-CM-API-response/m-p/412457#M253460</guid>
      <dc:creator>cdebernardi</dc:creator>
      <dc:date>2025-09-24T20:07:36Z</dc:date>
    </item>
  </channel>
</rss>

