@Override public boolean isTraceEnabled() { return logger.isTraceEnabled(); }
public static Profiler createIfTrace(Logger logger) { if (logger.isTraceEnabled()) { return create(logger); } return NullProfiler.NULL_INSTANCE; }
public static Profiler createIfTrace(Logger logger) { if (logger.isTraceEnabled()) { return create(logger); } return NullProfiler.NULL_INSTANCE; }
private static boolean shouldLog(Logger logger, LoggerLevel level) { if (level == LoggerLevel.TRACE && !logger.isTraceEnabled()) { return false; } return level != LoggerLevel.DEBUG || logger.isDebugEnabled(); }
/** * Logs a TRACE message, which is only to be constructed if the logging level * is such that the message will actually be logged. * <p> * TRACE messages must * be valuable for diagnosing production problems. They must not be used for development debugging. * They can significantly slow down performances. The standard use-case is logging of * SQL and Elasticsearch requests. * @param msgSupplier A function, which when called, produces the desired log message * @since 6.3 */ default void trace(Supplier<String> msgSupplier) { if (isTraceEnabled()) { trace(msgSupplier.get()); } }
@Override public boolean isTraceEnabled() { return logger.isTraceEnabled(); }
public static Profiler createIfTrace(Logger logger) { if (logger.isTraceEnabled()) { return create(logger); } return NullProfiler.NULL_INSTANCE; }
public static Profiler createIfTrace(Logger logger) { if (logger.isTraceEnabled()) { return create(logger); } return NullProfiler.NULL_INSTANCE; }
private static boolean shouldLog(Logger logger, LoggerLevel level) { if (level == LoggerLevel.TRACE && !logger.isTraceEnabled()) { return false; } return level != LoggerLevel.DEBUG || logger.isDebugEnabled(); }
public static Profiler createIfTrace(Logger logger) { if (logger.isTraceEnabled()) { return create(logger); } return NullProfiler.NULL_INSTANCE; }
/** * Logs a TRACE message, which is only to be constructed if the logging level * is such that the message will actually be logged. * <p> * TRACE messages must * be valuable for diagnosing production problems. They must not be used for development debugging. * They can significantly slow down performances. The standard use-case is logging of * SQL and Elasticsearch requests. * @param msgSupplier A function, which when called, produces the desired log message * @since 6.3 */ default void trace(Supplier<String> msgSupplier) { if (isTraceEnabled()) { trace(msgSupplier.get()); } }