Created 03-26-2022 11:59 PM
Hi
I am using many InvokeHTTP processors for sending APIs to a cloud service (complex flow in NIFI)
I need to know how many requests NIFI is sending per minute (as I am paying by CallsPerMinutes).
Besides the provenance window, where are the logs/files (on the Linux machine) showing those calls? I need to be able to read them and then I could analyze them.
Thank you,
Tamir
Created 03-28-2022 03:49 AM
Answer to first question: you can use Reporting Task's to get processor status and enrich/trim the information as per you need with in NiFi
or you can configure downstream queue for relationship Original from InvokeHTTP procesor and have count on that ,something similar on the lines https://community.cloudera.com/t5/Support-Questions/NiFi-Count-Fileflows-via-attribute/m-p/178860
Answer to Second question : NiFi stores processor related logs under nifi-app.log file which is by default located under /var/log/nifi/ , By default NiFi Processors only prints logs for start and stop operations and Warning and Error associated to the processors , user wont be seeing any events on what is being processed by processor until DEBUG is enabled for Processor class, which is only recommended to use in case of detailed information needed while troubleshooting any problem for short term period. You can filter specific component logs in nifi-app.log by using their component ID.
Thank You.
Created 03-28-2022 03:49 AM
Answer to first question: you can use Reporting Task's to get processor status and enrich/trim the information as per you need with in NiFi
or you can configure downstream queue for relationship Original from InvokeHTTP procesor and have count on that ,something similar on the lines https://community.cloudera.com/t5/Support-Questions/NiFi-Count-Fileflows-via-attribute/m-p/178860
Answer to Second question : NiFi stores processor related logs under nifi-app.log file which is by default located under /var/log/nifi/ , By default NiFi Processors only prints logs for start and stop operations and Warning and Error associated to the processors , user wont be seeing any events on what is being processed by processor until DEBUG is enabled for Processor class, which is only recommended to use in case of detailed information needed while troubleshooting any problem for short term period. You can filter specific component logs in nifi-app.log by using their component ID.
Thank You.
Created 03-31-2022 10:10 PM
Hi @Tamiri, Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.
Regards,
Vidya Sargur,