@jI-mi, Did the response help answer your question? If so, please consider marking it as the solution so others can easily find it later. ... View more

Hello @Sid17,  This looks very similar to what we see here:  https://community.cloudera.com/t5/Support-Questions/Jolt-spec-to-flatten-the-nested-JSON/m-p/399054#M250380  Can you take a look on that and see if it helps?  ... View more

@hckorkmaz01  @vafs provided a couple excellent options already. As a third option, you could utilize the SiteToSiteStatusReportingTask.  You can configure this NiFi reporting task to send metrics for only connections and you can add a regex to limited the number of connections returned (this requires renaming the desired connections so you have more granular control with the regex).  This Reporting task can be configured to send to a remote input port on on the same NiFi.   This Reporting task will execute the query on each host in your NiFi Cluster and send results to the the desired Site-To-Site remote input port.   So in a three node NiFi cluster three FlowFiles will be produced and sent with Json content for connection(s) you filtered on.   This way you can see what is queued per node.  Limitations to monitoring connections in this way exist.  Keep in mind that you are grabbing a snapshot at one specific moment in time.  So if the downstream component of this monitored connection is running, the connection stat would have likely changed by the time you got the last status details.   Now if you are using this to monitor flow dead-ends where you don't expect FlowFiles to ever accumulate, that is perhaps a valid use case. Example json output placed in FlowFile: [ { "statusId" : "27b01368-8280-4e5e-ac22-0e749c46fe17", "timestampMillis" : 1771336855410, "timestamp" : "2026-02-17T14:00:55.410Z", "actorHostname" : "nifi-node-1", "componentType" : "Connection", "componentName" : "Monitored-success", "parentId" : "603017c1-0197-1000-0000-000013171e7c", "parentName" : "test", "parentPath" : "NiFi Flow / test", "platform" : "nifi", "application" : "NiFi Flow", "componentId" : "508a2293-019a-1000-ffff-fffff15dc582", "sourceId" : "5089d4ab-019a-1000-ffff-ffff9b682ab3", "sourceName" : "UpdateAttribute", "destinationId" : "4dc23b89-25b0-1eff-b974-6fe5425c283f", "destinationName" : "UpdateAttribute", "maxQueuedBytes" : 0, "maxQueuedCount" : 0, "queuedBytes" : 30720, "queuedCount" : 30, "inputBytes" : 0, "inputCount" : 0, "outputBytes" : 0, "outputCount" : 0, "backPressureBytesThreshold" : 1073741824, "backPressureObjectThreshold" : 10000, "backPressureDataSizeThreshold" : "1 GB", "isBackPressureEnabled" : "false" } ]   IMPORTANT NOTE: I'd also like to point out that Apache NiFi 1.18 was released back in 2021 and newer releases have addressed many bugs and CVEs.  I strongly encourage you to transition to a newer version of Apache NiFi.  If you aren't ready to migrate to the newer Apache NiFi 2.x major release versions, you can still easily upgrade to last Apache NiFi 1.x major release version (1.28.0). Please help our community grow. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt ... View more

Hello @aaaver,  Just wanted to see if you can share little bit more details, for example, the NiFi version and if your using the CFM provided by Cloudera.  Have you followed these steps from the documentation?  https://docs.cloudera.com/cfm-operator/2.11.0/configure-nifi-cr/topics/cfm-op-configure-nifi-cr-oidc-auth.html ... View more

Hello @Hasib1971,  Are you still facing an issue or that was what solved your error?  If you still have an issue, please open a new thread so we can help you there.  ... View more

Hello @IgorSpryzhkov,  Let me see if I can help with your questions:  1. How to get list of Process Groups in the root and in Each PG? For this, you may be able to get the information with this API:  GET /process-groups/{id}/process-groups https://nifi.apache.org/docs/nifi-docs/rest-api/index.html    2. How to get list of Processors in Each PG?   For this one, this other API request may get you the info:  GET /process-groups/{id}/processors   3. How to organize in Groovy cycles for scan PGs? In NiFi ExecuteScript (Groovy), you can call the API recursively.  So you should be able order the logic there to fit what you need.    4. How to save / read data in/from Groovy dictionary /  NiFi cache? You can use any of these options: - DistributedMapCache (preferred if cluster, can use processors such as PutDistributedMapCache and FetchDistributedMapCache). - File-based persistence (write JSON file to disk). - FlowFile attributes (if just passing data). ... View more

@FGhidotti I have reached out via DM with further steps, thank you! ... View more

Hello @HoangNguyen,  The difference I see is that your queries does not match.  During all the queries I see this:  ,e.tsn as ticketserialnumber But on the SQL after the "/* Start Here */" it is different:  ,e.tsn as tsn On this type of queries you should always match the order and types.  ... View more

Hello @Chetan_mn,  I was checking and the entrypoint for this kind of scenarios should be start.sh, that should call everything you need to start it.  https://hub.docker.com/layers/apache/nifi/2.4.0/images/sha256-e8ca069f1533e6ee52d706fa3395ea16fe6f29468c7c6234a3f1c6232b912704 Do you have any error log that can give us more clues here?  ... View more

Hello @Alf015,  I found two thing that may be causing this issue.  First, the "vault.namespace" should not have the "/" at the end:  https://docs.spring.io/spring-vault/docs/2.3.x/reference/html/#vault.core.environment-vault-configuration On the Paramenter Provider, "key value path" should be only "secret", all the rest is taken from the header.  https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-hashicorp-vault-nar/1.28.0/org.apache.nifi.vault.hashicorp.HashiCorpVaultParameterProvider/  Try those changes and let us know if this fails.  If it does, maybe the Debug level for those modules can provide more information:  <logger name="org.apache.nifi.vault" level="DEBUG"/> <logger name="org.apache.nifi.parameter" level="DEBUG"/> <logger name="org.springframework.vault" level="DEBUG"/> ... View more