One point for using the isDebugEnabled (or any of the other level-checking
methods) is that if, in the values being logged, there is string
concatenation happening in the log.{level} statement itself. The cost of
that is paid whether the level is enabled or not. Even with parameterized
logging, if
Hi,
To answer to your question, Nifi has a context logger which is mapped to
logback.xml file. Generally INFO level of log is defaulted in nifi-app.logs.
In your code, you can simple use getLogger().debug("your message") or INFO,
ERROR,WARN etc to enable the logging into nifi-app.log with componen
Hi,
Logging level is set in logback.xml. To change the logging level for a given
logger/package/class, you must modify that file. See [1] for more details.
In your code example, you are creating the logger correctly using the
LoggerFactory. All NiFi Frameworks and extensions use the slf4j API,
Good morning. I am confused about logging levels from within java code that
defines a nar.
I have a java class file AMQPWorker.java, within which I establish a logger
used throughout my nar. This is what I inherited in the class:
abstract class AMQPWorker implements AutoCloseable {
private f
