<?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: how to see status of process instance running on nifi in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/how-to-see-status-of-process-instance-running-on-nifi/m-p/231820#M193663</link>
    <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/80325/neerajsha.html" nodeid="80325"&gt;@neeraj sharma&lt;/A&gt; &lt;/P&gt;&lt;P&gt;*** Forum tip:  Please try to avoid responding to an Answer by starting a new answer.  Instead use the "add comment" tp respond to en existing answer.  There is no guaranteed order to different answers which can make following a response thread difficult especially when multiple people are trying to assist you.&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;P&gt;NiFi Process Groups have no logical binding to a "process".  It is just a logical grouping of components on the canvas.  Under the hood, NiFi simply has a collection of interconnected components that are being scheduled to execute based on each components configuration.  There is no status based on a collection of components completing an operation on a specific FlowFile.  So you would need to look at the status of individual processor components.&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;P&gt;You may be able to extract the relevant information you are looking for by using the SiteToSiteBulletinReportingTask (get errors when failures occur) and/or SiteToSiteProvenanceReprotingTask (get info based on FlowFile events like create, drop, modify, etc..).&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Matt&lt;/P&gt;</description>
    <pubDate>Tue, 03 Jul 2018 03:09:00 GMT</pubDate>
    <dc:creator>MattWho</dc:creator>
    <dc:date>2018-07-03T03:09:00Z</dc:date>
  </channel>
</rss>

