Class LoggingEmitter
java.lang.Object
org.apache.druid.java.util.emitter.core.LoggingEmitter
- All Implemented Interfaces:
Closeable,Flushable,AutoCloseable,Emitter
-
Nested Class Summary
Nested Classes -
Constructor Summary
ConstructorsConstructorDescriptionLoggingEmitter(Logger log, LoggingEmitter.Level level, com.fasterxml.jackson.databind.ObjectMapper jsonMapper) LoggingEmitter(Logger log, LoggingEmitter.Level level, com.fasterxml.jackson.databind.ObjectMapper jsonMapper, boolean shouldFilterMetrics, String allowedMetricsPath) LoggingEmitter(LoggingEmitterConfig config, com.fasterxml.jackson.databind.ObjectMapper jsonMapper) -
Method Summary
-
Constructor Details
-
LoggingEmitter
public LoggingEmitter(LoggingEmitterConfig config, com.fasterxml.jackson.databind.ObjectMapper jsonMapper) -
LoggingEmitter
public LoggingEmitter(Logger log, LoggingEmitter.Level level, com.fasterxml.jackson.databind.ObjectMapper jsonMapper) -
LoggingEmitter
public LoggingEmitter(Logger log, LoggingEmitter.Level level, com.fasterxml.jackson.databind.ObjectMapper jsonMapper, boolean shouldFilterMetrics, @Nullable String allowedMetricsPath)
-
-
Method Details
-
start
public void start() -
emit
Description copied from interface:EmitterEmit an event. This method must not throw exceptions or block. If an implementation receives too many events and internal queues fill up, it should drop events rather than blocking or consuming excessive memory. If an implementation receives input it considers to be invalid, or has an internal problem, it should deal with that by logging a warning rather than throwing an exception. Implementations that log warnings should consider throttling warnings to avoid excessive logs, since a busy Druid cluster can emit a high volume of metric events. -
flush
public void flush() -
close
public void close() -
toString
-