Hi Minh, No - you can configure logging for any Java class, more or less. So that would equate to probably tens of thousands of possible loggers that you could configure. Of course, they are hierarchical, though, so you could configure, for example, “org.apache.nifi.processors” and that should affect all processors. You could also go another level down, and configure perhaps for “org.apache.nifi.processors.aws” or “org.apache.nifi.processors.aws.s3”.
Thanks -Mark On Nov 14, 2023, at 9:37 AM, e-soci...@gmx.fr<mailto:e-soci...@gmx.fr> wrote: Hello Mark, Have we got the documentation about exhaustive list about logger we got have in NIFI ? Regards Minh Envoyé: mardi 14 novembre 2023 à 15:25 De: "Mark Payne" <marka...@hotmail.com<mailto:marka...@hotmail.com>> À: "users" <users@nifi.apache.org<mailto:users@nifi.apache.org>> Objet: Re: ListSFTP Processor CRON doesn't start Hi Quentin, What is the CRON schedule that you configured? What version of NiFi are you running? You’ll not see any debug related logs for that Processor by changing its log level, as the Processor is not responsible for scheduling itself. But you can enable DEBUG level logs for org.apache.nifi.controller.scheduling.QuartzSchedulingAgent and that will provide a debug log each time the Processor runs, indicating when it’s expected to run again. Thanks -Mark > On Nov 14, 2023, at 2:28 AM, Quentin HORNEMAN GUTTON > <qhornemangut...@gmail.com<mailto:qhornemangut...@gmail.com>> wrote: > > Hello, > > I am facing an issue that I am having difficulty resolving. I have a ListSFTP > processor that is supposed to run every day at 12:15 AM, but it is not > launching. I added TRACE logs to this type of processor, but since it is not > launching, I cannot determine what is happening. If I change the launch time > of the processor (for example, to 04:00 PM), it launches successfully. This > is a NiFi cluster running on Redhat. Does anyone have an idea of how I can > identify the root cause of this processor not launching ? > > Best regards,