Package io.quarkus.logging.gelf
Class GelfConfig
java.lang.Object
io.quarkus.logging.gelf.GelfConfig
-
Field Summary
FieldsModifier and TypeFieldDescriptionPost additional fields.Dynamic MDC Fields allows you to extract MDC values based on one or more regular expressions.Pattern-based type specification for additional and MDC fields.booleanDetermine whether to enable the GELF logging handlerbooleanWhether to post Stack-Trace to StackTrace field.Name of the facility.booleanWhether to perform Stack-Trace filteringHostname/IP-Address of the Logstash/Graylog Host By default it uses UDP, prepend tcp: to the hostname to switch to TCP, example: "tcp:localhost"booleanWhether to include all fields from the MDC.booleanInclude source code locationbooleanInclude message parameters from the log eventThe logging-gelf log level.intMaximum message size (in bytes).Send additional fields whose values are obtained from MDC.Origin hostnameintThe portbooleanBypass hostname resolution.intOnly used when `extractStackTrace` is `true`.Java date pattern, seeSimpleDateFormatGELF version: 1.0 or 1.1 -
Constructor Summary
Constructors -
Method Summary
-
Field Details
-
enabled
Determine whether to enable the GELF logging handler -
host
Hostname/IP-Address of the Logstash/Graylog Host By default it uses UDP, prepend tcp: to the hostname to switch to TCP, example: "tcp:localhost" -
port
The port -
version
GELF version: 1.0 or 1.1 -
extractStackTrace
Whether to post Stack-Trace to StackTrace field. -
stackTraceThrowableReference
Only used when `extractStackTrace` is `true`. A value of 0 will extract the whole stack trace. Any positive value will walk the cause chain: 1 corresponds with exception.getCause(), 2 with exception.getCause().getCause(), ... Negative throwable reference walk the exception chain from the root cause side: -1 will extract the root cause, -2 the exception wrapping the root cause, ... -
filterStackTrace
Whether to perform Stack-Trace filtering -
timestampPattern
Java date pattern, seeSimpleDateFormat -
level
The logging-gelf log level. -
facility
Name of the facility. -
additionalField
@ConfigItem @ConfigDocMapKey("field-name") @ConfigDocSection public Map<String,AdditionalFieldConfig> additionalFieldPost additional fields. You can add static fields to each log event in the following form:quarkus.log.handler.gelf.additional-field.field1.value=value1 quarkus.log.handler.gelf.additional-field.field1.type=String
-
includeFullMdc
Whether to include all fields from the MDC. -
mdcFields
Send additional fields whose values are obtained from MDC. Name of the Fields are comma-separated. Example: mdcFields=Application,Version,SomeOtherFieldName -
dynamicMdcFields
Dynamic MDC Fields allows you to extract MDC values based on one or more regular expressions. Multiple regexes are comma-separated. The name of the MDC entry is used as GELF field name. -
dynamicMdcFieldTypes
Pattern-based type specification for additional and MDC fields. Key-value pairs are comma-separated. Example: my_field.*=String,business\..*\.field=double -
maximumMessageSize
Maximum message size (in bytes). If the message size is exceeded, the appender will submit the message in multiple chunks. -
includeLogMessageParameters
Include message parameters from the log event -
includeLocation
Include source code location -
originHost
Origin hostname -
skipHostnameResolution
Bypass hostname resolution. If you didn't set theoriginHostproperty, and resolution is disabled, the value “unknown” will be used as hostname
-
-
Constructor Details
-
GelfConfig
public GelfConfig()
-