<?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: QRS API endpoint for node status in Integration, Extension &amp; APIs</title>
    <link>https://community.qlik.com/t5/Integration-Extension-APIs/QRS-API-endpoint-for-node-status/m-p/1567005#M10311</link>
    <description>Thanks! that helped &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;</description>
    <pubDate>Tue, 09 Apr 2019 14:19:10 GMT</pubDate>
    <dc:creator>aadil_madarveet</dc:creator>
    <dc:date>2019-04-09T14:19:10Z</dc:date>
    <item>
      <title>QRS API endpoint for node status</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/QRS-API-endpoint-for-node-status/m-p/1562841#M10252</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;Does anyone know the api endpoint to check if a node is offline or online.&lt;/P&gt;&lt;P&gt;Right now i have to login to QMC to discover that one of the node has gone offline for some reason.&lt;/P&gt;&lt;P&gt;I have tried these two, but doesn't seem to return anything that would tell me if its online or offline.&lt;/P&gt;&lt;P&gt;/servernodeconfiguration/full&lt;/P&gt;&lt;P&gt;/servernodeheartbeat/full&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Aadil&lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 21:09:29 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/QRS-API-endpoint-for-node-status/m-p/1562841#M10252</guid>
      <dc:creator>aadil_madarveet</dc:creator>
      <dc:date>2024-11-16T21:09:29Z</dc:date>
    </item>
    <item>
      <title>Re: QRS API endpoint for node status</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/QRS-API-endpoint-for-node-status/m-p/1562866#M10254</link>
      <description>&lt;P&gt;By calling &lt;FONT face="courier new,courier"&gt;GET&amp;nbsp;/qrs/ServiceStatus/full&lt;/FONT&gt;. We have three key values we're interested in:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;serverNodeConfiguration.hostname: This provides the host we are analyzing&lt;/LI&gt;
&lt;LI&gt;serviceType: This provides the service&lt;/LI&gt;
&lt;LI&gt;serviceState: This provides the state of the service&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;To decipher the&amp;nbsp;serviceType and&amp;nbsp;serviceState elements and map their enums to the semantic values we call &lt;FONT face="courier new,courier"&gt;GET&amp;nbsp;/qrs/about/openapi/main&lt;/FONT&gt; and narrow in on the&amp;nbsp;ServiceStatus elements like so:&lt;/P&gt;
&lt;PRE&gt;   "ServiceStatus": {
      "type": "object",
      "properties": {
        "id": {
          "type": "string",
          "format": "uuid"
        },
        "createdDate": {
          "type": "string",
          "format": "date-time"
        },
        "modifiedDate": {
          "type": "string",
          "format": "date-time"
        },
        "modifiedByUserName": {
          "type": "string"
        },
        "schemaPath": {
          "type": "string"
        },
        "privileges": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "serverNodeConfiguration": {
          "$ref": "#/definitions/ServerNodeConfigurationCondensed"
        },
        "serviceType": {
          "type": "integer",
          "enum": [
            0,
            1,
            2,
            3,
            4,
            5
          ],
          "x-enumNames": [
            "Repository",
            "Proxy",
            "Scheduler",
            "Engine",
            "AppMigration",
            "Printing"
          ]
        },
        "serviceState": {
          "type": "integer",
          "enum": [
            0,
            1,
            2,
            3,
            4,
            5
          ],
          "x-enumNames": [
            "Initializing",
            "CertificatesNotInstalled",
            "Running",
            "NoCommunication",
            "Disabled",
            "Unknown"
          ]
        },
        "timestamp": {
          "type": "string",
          "format": "date-time"
        }
      },
      "required": [
        "serverNodeConfiguration",
        "serviceType",
        "serviceState"
      ],
      "x-qlik-stability": "Locked"
    }&lt;/PRE&gt;
&lt;P&gt;From there you can map the nodes, their service(s), and their statuses to semantic values.&lt;/P&gt;</description>
      <pubDate>Fri, 29 Mar 2019 11:54:37 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/QRS-API-endpoint-for-node-status/m-p/1562866#M10254</guid>
      <dc:creator>Levi_Turner</dc:creator>
      <dc:date>2019-03-29T11:54:37Z</dc:date>
    </item>
    <item>
      <title>Re: QRS API endpoint for node status</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/QRS-API-endpoint-for-node-status/m-p/1567005#M10311</link>
      <description>Thanks! that helped &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;</description>
      <pubDate>Tue, 09 Apr 2019 14:19:10 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/QRS-API-endpoint-for-node-status/m-p/1567005#M10311</guid>
      <dc:creator>aadil_madarveet</dc:creator>
      <dc:date>2019-04-09T14:19:10Z</dc:date>
    </item>
  </channel>
</rss>

