code
stringlengths 23
201k
| docstring
stringlengths 17
96.2k
| func_name
stringlengths 0
235
| language
stringclasses 1
value | repo
stringlengths 8
72
| path
stringlengths 11
317
| url
stringlengths 57
377
| license
stringclasses 7
values |
|---|---|---|---|---|---|---|---|
public void setAdditionalFields(String spec) {
ConfigurationSupport.setAdditionalFields(spec, gelfMessageAssembler);
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"Time": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
</ul>
@author Greg Peterson
@since 1.14.0
|
setAdditionalFields
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfFormatter.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfFormatter.java
|
MIT
|
public void setAdditionalFieldTypes(String spec) {
ConfigurationSupport.setAdditionalFieldTypes(spec, gelfMessageAssembler);
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"Time": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
</ul>
@author Greg Peterson
@since 1.14.0
|
setAdditionalFieldTypes
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfFormatter.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfFormatter.java
|
MIT
|
public String getOriginHost() {
return gelfMessageAssembler.getOriginHost();
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"Time": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
</ul>
@author Greg Peterson
@since 1.14.0
|
getOriginHost
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfFormatter.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfFormatter.java
|
MIT
|
public String getFacility() {
return gelfMessageAssembler.getFacility();
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"Time": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
</ul>
@author Greg Peterson
@since 1.14.0
|
getFacility
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfFormatter.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfFormatter.java
|
MIT
|
public String getExtractStackTrace() {
return gelfMessageAssembler.getExtractStackTrace();
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"Time": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
</ul>
@author Greg Peterson
@since 1.14.0
|
getExtractStackTrace
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfFormatter.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfFormatter.java
|
MIT
|
public boolean isFilterStackTrace() {
return gelfMessageAssembler.isFilterStackTrace();
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"Time": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
</ul>
@author Greg Peterson
@since 1.14.0
|
isFilterStackTrace
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfFormatter.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfFormatter.java
|
MIT
|
public boolean isIncludeLogMessageParameters() {
return gelfMessageAssembler.isIncludeLogMessageParameters();
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"Time": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
</ul>
@author Greg Peterson
@since 1.14.0
|
isIncludeLogMessageParameters
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfFormatter.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfFormatter.java
|
MIT
|
public boolean isIncludeLocation() {
return gelfMessageAssembler.isIncludeLocation();
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"Time": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
</ul>
@author Greg Peterson
@since 1.14.0
|
isIncludeLocation
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfFormatter.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfFormatter.java
|
MIT
|
public String getTimestampPattern() {
return gelfMessageAssembler.getTimestampPattern();
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"Time": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
</ul>
@author Greg Peterson
@since 1.14.0
|
getTimestampPattern
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfFormatter.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfFormatter.java
|
MIT
|
public String getVersion() {
return gelfMessageAssembler.getVersion();
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"Time": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
</ul>
@author Greg Peterson
@since 1.14.0
|
getVersion
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfFormatter.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfFormatter.java
|
MIT
|
public String getLineBreak() {
return lineBreak;
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"Time": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
</ul>
@author Greg Peterson
@since 1.14.0
|
getLineBreak
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfFormatter.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfFormatter.java
|
MIT
|
public void setLineBreak(String lineBreak) {
this.lineBreak = lineBreak;
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"Time": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
</ul>
@author Greg Peterson
@since 1.14.0
|
setLineBreak
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfFormatter.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfFormatter.java
|
MIT
|
protected void initializeDefaultFields() {
gelfMessageAssembler.addFields(LogMessageField.getDefaultMapping(Time, Severity, ThreadName, SourceClassName,
SourceMethodName, SourceSimpleClassName, LoggerName));
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>level (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalField.(number) (Optional): Post additional fields. Eg. .GelfLogHandler.additionalField.0=fieldName=Value</li>
</ul>
The {@link #publish(LogRecord)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
initializeDefaultFields
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
MIT
|
protected GelfMessageAssembler createGelfMessageAssembler() {
return new GelfMessageAssembler();
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>level (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalField.(number) (Optional): Post additional fields. Eg. .GelfLogHandler.additionalField.0=fieldName=Value</li>
</ul>
The {@link #publish(LogRecord)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
createGelfMessageAssembler
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
MIT
|
@Override
public void flush() {
// nothing to do
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>level (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalField.(number) (Optional): Post additional fields. Eg. .GelfLogHandler.additionalField.0=fieldName=Value</li>
</ul>
The {@link #publish(LogRecord)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
flush
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
MIT
|
@Override
public void publish(final LogRecord record) {
if (!isLoggable(record)) {
return;
}
try {
if (null == gelfSender) {
synchronized (this) {
if (null == gelfSender) {
gelfSender = createGelfSender();
}
}
}
} catch (Exception e) {
reportError("Could not send GELF message: " + e.getMessage(), e, ErrorManager.OPEN_FAILURE);
return;
}
try {
GelfMessage message = createGelfMessage(record);
if (!message.isValid()) {
reportError("GELF Message is invalid: " + message.toJson(), null, ErrorManager.WRITE_FAILURE);
return;
}
if (null == gelfSender || !gelfSender.sendMessage(message)) {
reportError("Could not send GELF message", null, ErrorManager.WRITE_FAILURE);
}
} catch (Exception e) {
reportError("Could not send GELF message: " + e.getMessage(), e, ErrorManager.FORMAT_FAILURE);
}
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>level (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalField.(number) (Optional): Post additional fields. Eg. .GelfLogHandler.additionalField.0=fieldName=Value</li>
</ul>
The {@link #publish(LogRecord)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
publish
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
MIT
|
protected GelfSender createGelfSender() {
return GelfSenderFactory.createSender(gelfMessageAssembler, errorReporter, Collections.<String, Object>emptyMap());
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>level (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalField.(number) (Optional): Post additional fields. Eg. .GelfLogHandler.additionalField.0=fieldName=Value</li>
</ul>
The {@link #publish(LogRecord)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
createGelfSender
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
MIT
|
@Override
public void reportError(String message, Exception e) {
reportError(message, e, ErrorManager.GENERIC_FAILURE);
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>level (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalField.(number) (Optional): Post additional fields. Eg. .GelfLogHandler.additionalField.0=fieldName=Value</li>
</ul>
The {@link #publish(LogRecord)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
reportError
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
MIT
|
@Override
public void close() {
if (null != gelfSender) {
Closer.close(gelfSender);
gelfSender = null;
}
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>level (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalField.(number) (Optional): Post additional fields. Eg. .GelfLogHandler.additionalField.0=fieldName=Value</li>
</ul>
The {@link #publish(LogRecord)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
close
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
MIT
|
protected GelfMessage createGelfMessage(final LogRecord record) {
return gelfMessageAssembler.createGelfMessage(new JulLogEvent(record));
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>level (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalField.(number) (Optional): Post additional fields. Eg. .GelfLogHandler.additionalField.0=fieldName=Value</li>
</ul>
The {@link #publish(LogRecord)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
createGelfMessage
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
MIT
|
public void setAdditionalFields(String spec) {
ConfigurationSupport.setAdditionalFields(spec, gelfMessageAssembler);
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>level (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalField.(number) (Optional): Post additional fields. Eg. .GelfLogHandler.additionalField.0=fieldName=Value</li>
</ul>
The {@link #publish(LogRecord)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
setAdditionalFields
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
MIT
|
public void setAdditionalFieldTypes(String spec) {
ConfigurationSupport.setAdditionalFieldTypes(spec, gelfMessageAssembler);
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>level (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalField.(number) (Optional): Post additional fields. Eg. .GelfLogHandler.additionalField.0=fieldName=Value</li>
</ul>
The {@link #publish(LogRecord)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
setAdditionalFieldTypes
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
MIT
|
public void setMdcFields(String spec) {
ConfigurationSupport.setMdcFields(spec, gelfMessageAssembler);
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>level (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalField.(number) (Optional): Post additional fields. Eg. .GelfLogHandler.additionalField.0=fieldName=Value</li>
</ul>
The {@link #publish(LogRecord)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
setMdcFields
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
MIT
|
public void setDynamicMdcFields(String spec) {
ConfigurationSupport.setDynamicMdcFields(spec, gelfMessageAssembler);
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>level (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalField.(number) (Optional): Post additional fields. Eg. .GelfLogHandler.additionalField.0=fieldName=Value</li>
</ul>
The {@link #publish(LogRecord)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
setDynamicMdcFields
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
MIT
|
public void setDynamicMdcFieldTypes(String spec) {
ConfigurationSupport.setDynamicMdcFieldTypes(spec, gelfMessageAssembler);
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>level (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalField.(number) (Optional): Post additional fields. Eg. .GelfLogHandler.additionalField.0=fieldName=Value</li>
</ul>
The {@link #publish(LogRecord)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
setDynamicMdcFieldTypes
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
MIT
|
public String getGraylogHost() {
return gelfMessageAssembler.getHost();
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>level (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalField.(number) (Optional): Post additional fields. Eg. .GelfLogHandler.additionalField.0=fieldName=Value</li>
</ul>
The {@link #publish(LogRecord)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
getGraylogHost
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
MIT
|
public String getOriginHost() {
return gelfMessageAssembler.getOriginHost();
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>level (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalField.(number) (Optional): Post additional fields. Eg. .GelfLogHandler.additionalField.0=fieldName=Value</li>
</ul>
The {@link #publish(LogRecord)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
getOriginHost
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
MIT
|
public String getHost() {
return gelfMessageAssembler.getHost();
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>level (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalField.(number) (Optional): Post additional fields. Eg. .GelfLogHandler.additionalField.0=fieldName=Value</li>
</ul>
The {@link #publish(LogRecord)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
getHost
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
MIT
|
public int getPort() {
return gelfMessageAssembler.getPort();
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>level (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalField.(number) (Optional): Post additional fields. Eg. .GelfLogHandler.additionalField.0=fieldName=Value</li>
</ul>
The {@link #publish(LogRecord)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
getPort
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
MIT
|
public int getGraylogPort() {
return gelfMessageAssembler.getPort();
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>level (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalField.(number) (Optional): Post additional fields. Eg. .GelfLogHandler.additionalField.0=fieldName=Value</li>
</ul>
The {@link #publish(LogRecord)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
getGraylogPort
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
MIT
|
public String getFacility() {
return gelfMessageAssembler.getFacility();
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>level (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalField.(number) (Optional): Post additional fields. Eg. .GelfLogHandler.additionalField.0=fieldName=Value</li>
</ul>
The {@link #publish(LogRecord)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
getFacility
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
MIT
|
public String getExtractStackTrace() {
return gelfMessageAssembler.getExtractStackTrace();
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>level (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalField.(number) (Optional): Post additional fields. Eg. .GelfLogHandler.additionalField.0=fieldName=Value</li>
</ul>
The {@link #publish(LogRecord)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
getExtractStackTrace
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
MIT
|
public boolean isFilterStackTrace() {
return gelfMessageAssembler.isFilterStackTrace();
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>level (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalField.(number) (Optional): Post additional fields. Eg. .GelfLogHandler.additionalField.0=fieldName=Value</li>
</ul>
The {@link #publish(LogRecord)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
isFilterStackTrace
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
MIT
|
public boolean isIncludeLogMessageParameters() {
return gelfMessageAssembler.isIncludeLogMessageParameters();
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>level (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalField.(number) (Optional): Post additional fields. Eg. .GelfLogHandler.additionalField.0=fieldName=Value</li>
</ul>
The {@link #publish(LogRecord)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
isIncludeLogMessageParameters
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
MIT
|
public boolean isIncludeLocation() {
return gelfMessageAssembler.isIncludeLocation();
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>level (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalField.(number) (Optional): Post additional fields. Eg. .GelfLogHandler.additionalField.0=fieldName=Value</li>
</ul>
The {@link #publish(LogRecord)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
isIncludeLocation
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
MIT
|
public String getTimestampPattern() {
return gelfMessageAssembler.getTimestampPattern();
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>level (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalField.(number) (Optional): Post additional fields. Eg. .GelfLogHandler.additionalField.0=fieldName=Value</li>
</ul>
The {@link #publish(LogRecord)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
getTimestampPattern
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
MIT
|
public int getMaximumMessageSize() {
return gelfMessageAssembler.getMaximumMessageSize();
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>level (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalField.(number) (Optional): Post additional fields. Eg. .GelfLogHandler.additionalField.0=fieldName=Value</li>
</ul>
The {@link #publish(LogRecord)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
getMaximumMessageSize
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
MIT
|
public String getVersion() {
return gelfMessageAssembler.getVersion();
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLogMessageParameters (Optional): Include message parameters from the log event (see
{@link LogRecord#getParameters()}, default true</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>level (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalField.(number) (Optional): Post additional fields. Eg. .GelfLogHandler.additionalField.0=fieldName=Value</li>
</ul>
The {@link #publish(LogRecord)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
getVersion
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/jul/GelfLogHandler.java
|
MIT
|
@Override
public String format(LoggingEvent loggingEvent) {
if (!wasSetFieldsCalled) {
addFields(SUPPORTED_FIELDS);
}
GelfMessage gelfMessage = gelfMessageAssembler.createGelfMessage(new Log4jLogEvent(loggingEvent));
return gelfMessage.toJson("") + lineBreak;
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"NDC": "ndc message",
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"MyTime": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName, NDC}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name. mdc.*,[mdc|MDC]fields</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the formatter:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
@author <a href="mailto:kai.geisselhardt@kaufland.com">Kai Geisselhardt</a>
@author Mark Paluch
|
format
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
MIT
|
@Override
public boolean ignoresThrowable() {
return false;
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"NDC": "ndc message",
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"MyTime": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName, NDC}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name. mdc.*,[mdc|MDC]fields</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the formatter:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
@author <a href="mailto:kai.geisselhardt@kaufland.com">Kai Geisselhardt</a>
@author Mark Paluch
|
ignoresThrowable
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
MIT
|
@Override
public void activateOptions() {
// nothing to do
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"NDC": "ndc message",
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"MyTime": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName, NDC}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name. mdc.*,[mdc|MDC]fields</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the formatter:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
@author <a href="mailto:kai.geisselhardt@kaufland.com">Kai Geisselhardt</a>
@author Mark Paluch
|
activateOptions
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
MIT
|
public void setFields(String fieldSpec) {
String[] properties = fieldSpec.split(MULTI_VALUE_DELIMITTER);
List<LogMessageField.NamedLogField> fields = new ArrayList<>();
for (String field : properties) {
LogMessageField.NamedLogField namedLogField = LogMessageField.NamedLogField.byName(field.trim());
if (namedLogField == null) {
throw new IllegalArgumentException("Cannot resolve field name '" + field
+ "' to a field. Supported field names are: " + SUPPORTED_FIELDS);
}
if (!SUPPORTED_FIELDS.contains(namedLogField)) {
throw new IllegalArgumentException("Field '" + field + "' is not supported. Supported field names are: "
+ SUPPORTED_FIELDS);
}
fields.add(namedLogField);
}
addFields(fields);
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"NDC": "ndc message",
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"MyTime": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName, NDC}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name. mdc.*,[mdc|MDC]fields</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the formatter:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
@author <a href="mailto:kai.geisselhardt@kaufland.com">Kai Geisselhardt</a>
@author Mark Paluch
|
setFields
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
MIT
|
private void addFields(Collection<LogMessageField.NamedLogField> fields) {
gelfMessageAssembler.addFields(LogMessageField.getDefaultMapping(fields
.toArray(new LogMessageField.NamedLogField[fields.size()])));
wasSetFieldsCalled = true;
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"NDC": "ndc message",
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"MyTime": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName, NDC}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name. mdc.*,[mdc|MDC]fields</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the formatter:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
@author <a href="mailto:kai.geisselhardt@kaufland.com">Kai Geisselhardt</a>
@author Mark Paluch
|
addFields
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
MIT
|
public void setAdditionalFields(String spec) {
ConfigurationSupport.setAdditionalFields(spec, gelfMessageAssembler);
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"NDC": "ndc message",
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"MyTime": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName, NDC}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name. mdc.*,[mdc|MDC]fields</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the formatter:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
@author <a href="mailto:kai.geisselhardt@kaufland.com">Kai Geisselhardt</a>
@author Mark Paluch
|
setAdditionalFields
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
MIT
|
public void setAdditionalFieldTypes(String spec) {
ConfigurationSupport.setAdditionalFieldTypes(spec, gelfMessageAssembler);
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"NDC": "ndc message",
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"MyTime": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName, NDC}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name. mdc.*,[mdc|MDC]fields</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the formatter:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
@author <a href="mailto:kai.geisselhardt@kaufland.com">Kai Geisselhardt</a>
@author Mark Paluch
|
setAdditionalFieldTypes
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
MIT
|
public void setMdcFields(String spec) {
ConfigurationSupport.setMdcFields(spec, gelfMessageAssembler);
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"NDC": "ndc message",
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"MyTime": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName, NDC}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name. mdc.*,[mdc|MDC]fields</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the formatter:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
@author <a href="mailto:kai.geisselhardt@kaufland.com">Kai Geisselhardt</a>
@author Mark Paluch
|
setMdcFields
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
MIT
|
public void setDynamicMdcFields(String spec) {
ConfigurationSupport.setDynamicMdcFields(spec, gelfMessageAssembler);
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"NDC": "ndc message",
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"MyTime": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName, NDC}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name. mdc.*,[mdc|MDC]fields</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the formatter:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
@author <a href="mailto:kai.geisselhardt@kaufland.com">Kai Geisselhardt</a>
@author Mark Paluch
|
setDynamicMdcFields
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
MIT
|
public void setDynamicMdcFieldTypes(String spec) {
ConfigurationSupport.setDynamicMdcFieldTypes(spec, gelfMessageAssembler);
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"NDC": "ndc message",
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"MyTime": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName, NDC}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name. mdc.*,[mdc|MDC]fields</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the formatter:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
@author <a href="mailto:kai.geisselhardt@kaufland.com">Kai Geisselhardt</a>
@author Mark Paluch
|
setDynamicMdcFieldTypes
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
MIT
|
public boolean isMdcProfiling() {
return gelfMessageAssembler.isMdcProfiling();
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"NDC": "ndc message",
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"MyTime": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName, NDC}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name. mdc.*,[mdc|MDC]fields</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the formatter:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
@author <a href="mailto:kai.geisselhardt@kaufland.com">Kai Geisselhardt</a>
@author Mark Paluch
|
isMdcProfiling
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
MIT
|
public boolean isIncludeFullMdc() {
return gelfMessageAssembler.isIncludeFullMdc();
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"NDC": "ndc message",
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"MyTime": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName, NDC}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name. mdc.*,[mdc|MDC]fields</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the formatter:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
@author <a href="mailto:kai.geisselhardt@kaufland.com">Kai Geisselhardt</a>
@author Mark Paluch
|
isIncludeFullMdc
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
MIT
|
public String getOriginHost() {
return gelfMessageAssembler.getOriginHost();
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"NDC": "ndc message",
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"MyTime": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName, NDC}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name. mdc.*,[mdc|MDC]fields</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the formatter:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
@author <a href="mailto:kai.geisselhardt@kaufland.com">Kai Geisselhardt</a>
@author Mark Paluch
|
getOriginHost
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
MIT
|
public String getFacility() {
return gelfMessageAssembler.getFacility();
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"NDC": "ndc message",
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"MyTime": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName, NDC}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name. mdc.*,[mdc|MDC]fields</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the formatter:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
@author <a href="mailto:kai.geisselhardt@kaufland.com">Kai Geisselhardt</a>
@author Mark Paluch
|
getFacility
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
MIT
|
public String getExtractStackTrace() {
return gelfMessageAssembler.getExtractStackTrace();
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"NDC": "ndc message",
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"MyTime": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName, NDC}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name. mdc.*,[mdc|MDC]fields</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the formatter:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
@author <a href="mailto:kai.geisselhardt@kaufland.com">Kai Geisselhardt</a>
@author Mark Paluch
|
getExtractStackTrace
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
MIT
|
public boolean isFilterStackTrace() {
return gelfMessageAssembler.isFilterStackTrace();
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"NDC": "ndc message",
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"MyTime": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName, NDC}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name. mdc.*,[mdc|MDC]fields</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the formatter:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
@author <a href="mailto:kai.geisselhardt@kaufland.com">Kai Geisselhardt</a>
@author Mark Paluch
|
isFilterStackTrace
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
MIT
|
public boolean isIncludeLocation() {
return gelfMessageAssembler.isIncludeLocation();
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"NDC": "ndc message",
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"MyTime": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName, NDC}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name. mdc.*,[mdc|MDC]fields</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the formatter:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
@author <a href="mailto:kai.geisselhardt@kaufland.com">Kai Geisselhardt</a>
@author Mark Paluch
|
isIncludeLocation
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
MIT
|
public String getTimestampPattern() {
return gelfMessageAssembler.getTimestampPattern();
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"NDC": "ndc message",
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"MyTime": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName, NDC}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name. mdc.*,[mdc|MDC]fields</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the formatter:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
@author <a href="mailto:kai.geisselhardt@kaufland.com">Kai Geisselhardt</a>
@author Mark Paluch
|
getTimestampPattern
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
MIT
|
public String getVersion() {
return gelfMessageAssembler.getVersion();
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"NDC": "ndc message",
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"MyTime": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName, NDC}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name. mdc.*,[mdc|MDC]fields</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the formatter:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
@author <a href="mailto:kai.geisselhardt@kaufland.com">Kai Geisselhardt</a>
@author Mark Paluch
|
getVersion
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
MIT
|
public String getLineBreak() {
return lineBreak;
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"NDC": "ndc message",
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"MyTime": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName, NDC}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name. mdc.*,[mdc|MDC]fields</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the formatter:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
@author <a href="mailto:kai.geisselhardt@kaufland.com">Kai Geisselhardt</a>
@author Mark Paluch
|
getLineBreak
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
MIT
|
public void setLineBreak(String lineBreak) {
this.lineBreak = lineBreak;
}
|
Log-Formatter for JSON using fields specified within GELF. This formatter will produce a JSON object for each log event.
Example:
<code>
{
"NDC": "ndc message",
"timestamp": "1439319236.722",
"SourceClassName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"SourceMethodName": "testDefaults",
"level": "6",
"SourceSimpleClassName": "WildFlyGelfLogFormatterTest",
"facility": "logstash-gelf",
"full_message": "foo bar test log message",
"short_message": "foo bar test log message",
"MySeverity": "INFO",
"LoggerName": "biz.paluch.logging.gelf.wildfly.WildFlyGelfLogFormatterTest",
"Thread": "main",
"MyTime": "2015-08-11 20:53:56,0722"
}
</code>
Following parameters are supported/needed:
<ul>
<li>lineBreak (Optional): End of line, platform dependent default value, see {@code System.getProperty("line.separator")}</li>
<li>fields (Optional): Comma-separated list of log event fields that should be included in the JSON. Defaults to
{@code Time, Severity, ThreadName, SourceClassName, SourceMethodName, SourceSimpleClassName, LoggerName, NDC}</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg. fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name. mdc.*,[mdc|MDC]fields</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the formatter:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
@author <a href="mailto:kai.geisselhardt@kaufland.com">Kai Geisselhardt</a>
@author Mark Paluch
|
setLineBreak
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLayout.java
|
MIT
|
@Override
protected void append(LoggingEvent event) {
if (event == null) {
return;
}
try {
GelfMessage message = createGelfMessage(event);
if (!message.isValid()) {
reportError("GELF Message is invalid: " + message.toJson(), null);
return;
}
if (null == gelfSender || !gelfSender.sendMessage(message)) {
reportError("Could not send GELF message", null);
}
} catch (Exception e) {
reportError("Could not send GELF message: " + e.getMessage(), e);
}
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>threshold (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg.
.GelfLogHandler.additionalFields=fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
mdcFields=Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name.</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the Log Appender:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
The {@link #append(LoggingEvent)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
append
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
MIT
|
protected GelfSender createGelfSender() {
return GelfSenderFactory.createSender(gelfMessageAssembler, errorReporter, Collections.<String, Object>emptyMap());
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>threshold (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg.
.GelfLogHandler.additionalFields=fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
mdcFields=Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name.</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the Log Appender:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
The {@link #append(LoggingEvent)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
createGelfSender
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
MIT
|
@Override
public void reportError(String message, Exception exception) {
errorHandler.error(message, exception, 0);
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>threshold (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg.
.GelfLogHandler.additionalFields=fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
mdcFields=Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name.</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the Log Appender:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
The {@link #append(LoggingEvent)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
reportError
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
MIT
|
@Override
public boolean requiresLayout() {
return false;
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>threshold (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg.
.GelfLogHandler.additionalFields=fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
mdcFields=Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name.</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the Log Appender:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
The {@link #append(LoggingEvent)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
requiresLayout
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
MIT
|
@Override
public void activateOptions() {
if (null == gelfSender) {
gelfSender = createGelfSender();
}
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>threshold (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg.
.GelfLogHandler.additionalFields=fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
mdcFields=Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name.</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the Log Appender:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
The {@link #append(LoggingEvent)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
activateOptions
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
MIT
|
@Override
public void close() {
if (null != gelfSender) {
Closer.close(gelfSender);
gelfSender = null;
}
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>threshold (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg.
.GelfLogHandler.additionalFields=fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
mdcFields=Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name.</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the Log Appender:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
The {@link #append(LoggingEvent)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
close
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
MIT
|
protected GelfMessage createGelfMessage(final LoggingEvent loggingEvent) {
return gelfMessageAssembler.createGelfMessage(new Log4jLogEvent(loggingEvent));
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>threshold (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg.
.GelfLogHandler.additionalFields=fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
mdcFields=Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name.</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the Log Appender:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
The {@link #append(LoggingEvent)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
createGelfMessage
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
MIT
|
public void setAdditionalFields(String spec) {
ConfigurationSupport.setAdditionalFields(spec, gelfMessageAssembler);
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>threshold (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg.
.GelfLogHandler.additionalFields=fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
mdcFields=Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name.</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the Log Appender:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
The {@link #append(LoggingEvent)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
setAdditionalFields
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
MIT
|
public void setAdditionalFieldTypes(String spec) {
ConfigurationSupport.setAdditionalFieldTypes(spec, gelfMessageAssembler);
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>threshold (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg.
.GelfLogHandler.additionalFields=fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
mdcFields=Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name.</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the Log Appender:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
The {@link #append(LoggingEvent)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
setAdditionalFieldTypes
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
MIT
|
public void setMdcFields(String spec) {
ConfigurationSupport.setMdcFields(spec, gelfMessageAssembler);
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>threshold (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg.
.GelfLogHandler.additionalFields=fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
mdcFields=Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name.</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the Log Appender:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
The {@link #append(LoggingEvent)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
setMdcFields
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
MIT
|
public void setDynamicMdcFields(String spec) {
ConfigurationSupport.setDynamicMdcFields(spec, gelfMessageAssembler);
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>threshold (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg.
.GelfLogHandler.additionalFields=fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
mdcFields=Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name.</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the Log Appender:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
The {@link #append(LoggingEvent)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
setDynamicMdcFields
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
MIT
|
public void setDynamicMdcFieldTypes(String spec) {
ConfigurationSupport.setDynamicMdcFieldTypes(spec, gelfMessageAssembler);
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>threshold (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg.
.GelfLogHandler.additionalFields=fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
mdcFields=Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name.</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the Log Appender:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
The {@link #append(LoggingEvent)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
setDynamicMdcFieldTypes
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
MIT
|
public String getGraylogHost() {
return gelfMessageAssembler.getHost();
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>threshold (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg.
.GelfLogHandler.additionalFields=fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
mdcFields=Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name.</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the Log Appender:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
The {@link #append(LoggingEvent)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
getGraylogHost
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
MIT
|
public int getGraylogPort() {
return gelfMessageAssembler.getPort();
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>threshold (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg.
.GelfLogHandler.additionalFields=fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
mdcFields=Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name.</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the Log Appender:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
The {@link #append(LoggingEvent)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
getGraylogPort
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
MIT
|
public String getHost() {
return gelfMessageAssembler.getHost();
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>threshold (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg.
.GelfLogHandler.additionalFields=fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
mdcFields=Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name.</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the Log Appender:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
The {@link #append(LoggingEvent)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
getHost
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
MIT
|
public int getPort() {
return gelfMessageAssembler.getPort();
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>threshold (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg.
.GelfLogHandler.additionalFields=fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
mdcFields=Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name.</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the Log Appender:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
The {@link #append(LoggingEvent)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
getPort
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
MIT
|
public String getOriginHost() {
return gelfMessageAssembler.getOriginHost();
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>threshold (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg.
.GelfLogHandler.additionalFields=fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
mdcFields=Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name.</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the Log Appender:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
The {@link #append(LoggingEvent)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
getOriginHost
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
MIT
|
public String getFacility() {
return gelfMessageAssembler.getFacility();
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>threshold (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg.
.GelfLogHandler.additionalFields=fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
mdcFields=Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name.</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the Log Appender:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
The {@link #append(LoggingEvent)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
getFacility
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
MIT
|
public String getExtractStackTrace() {
return gelfMessageAssembler.getExtractStackTrace();
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>threshold (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg.
.GelfLogHandler.additionalFields=fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
mdcFields=Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name.</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the Log Appender:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
The {@link #append(LoggingEvent)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
getExtractStackTrace
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
MIT
|
public boolean isFilterStackTrace() {
return gelfMessageAssembler.isFilterStackTrace();
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>threshold (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg.
.GelfLogHandler.additionalFields=fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
mdcFields=Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name.</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the Log Appender:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
The {@link #append(LoggingEvent)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
isFilterStackTrace
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
MIT
|
public boolean isIncludeLocation() {
return gelfMessageAssembler.isIncludeLocation();
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>threshold (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg.
.GelfLogHandler.additionalFields=fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
mdcFields=Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name.</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the Log Appender:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
The {@link #append(LoggingEvent)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
isIncludeLocation
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
MIT
|
public boolean isMdcProfiling() {
return gelfMessageAssembler.isMdcProfiling();
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>threshold (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg.
.GelfLogHandler.additionalFields=fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
mdcFields=Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name.</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the Log Appender:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
The {@link #append(LoggingEvent)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
isMdcProfiling
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
MIT
|
public String getTimestampPattern() {
return gelfMessageAssembler.getTimestampPattern();
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>threshold (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg.
.GelfLogHandler.additionalFields=fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
mdcFields=Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name.</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the Log Appender:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
The {@link #append(LoggingEvent)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
getTimestampPattern
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
MIT
|
public int getMaximumMessageSize() {
return gelfMessageAssembler.getMaximumMessageSize();
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>threshold (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg.
.GelfLogHandler.additionalFields=fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
mdcFields=Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name.</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the Log Appender:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
The {@link #append(LoggingEvent)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
getMaximumMessageSize
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
MIT
|
public boolean isIncludeFullMdc() {
return gelfMessageAssembler.isIncludeFullMdc();
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>threshold (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg.
.GelfLogHandler.additionalFields=fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
mdcFields=Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name.</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the Log Appender:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
The {@link #append(LoggingEvent)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
isIncludeFullMdc
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
MIT
|
public String getVersion() {
return gelfMessageAssembler.getVersion();
}
|
Logging-Handler for GELF (Graylog Extended Logging Format). This Java-Util-Logging Handler creates GELF Messages and posts
them using UDP (default) or TCP. Following parameters are supported/needed:
<ul>
<li>host (Mandatory): Hostname/IP-Address of the Logstash Host
<ul>
<li>(the host) for UDP, e.g. 127.0.0.1 or some.host.com</li>
<li>See docs for more details</li>
</ul>
</li>
<li>port (Optional): Port, default 12201</li>
<li>version (Optional): GELF Version 1.0 or 1.1, default 1.0</li>
<li>originHost (Optional): Originating Hostname, default FQDN Hostname</li>
<li>extractStackTrace (Optional): Post Stack-Trace to StackTrace field (true/false/throwable reference [0 = throwable, 1 =
throwable.cause, -1 = root cause]), default false</li>
<li>filterStackTrace (Optional): Perform Stack-Trace filtering (true/false), default false</li>
<li>includeLocation (Optional): Include source code location, default true</li>
<li>mdcProfiling (Optional): Perform Profiling (Call-Duration) based on MDC Data. See <a href="#mdcProfiling">MDC
Profiling</a>, default false</li>
<li>facility (Optional): Name of the Facility, default gelf-java</li>
<li>threshold (Optional): Log-Level, default INFO</li>
<li>filter (Optional): Class-Name of a Log-Filter, default none</li>
<li>additionalFields(number) (Optional): Post additional fields. Eg.
.GelfLogHandler.additionalFields=fieldName=Value,field2=value2</li>
<li>additionalFieldTypes (Optional): Type specification for additional and MDC fields. Supported types: String, long, Long,
double, Double and discover (default if not specified, discover field type on parseability). Eg. field=String,field2=double</li>
<li>mdcFields (Optional): Post additional fields, pull Values from MDC. Name of the Fields are comma-separated
mdcFields=Application,Version,SomeOtherFieldName</li>
<li>dynamicMdcFields (Optional): Dynamic MDC Fields allows you to extract MDC values based on one or more regular
expressions. Multiple regex are comma-separated. The name of the MDC entry is used as GELF field name.</li>
<li>dynamicMdcFieldTypes (Optional): Pattern-based type specification for additional and MDC fields. Key-value pairs are
comma-separated. Supported types: String, long, Long, double, Double. Eg. my_field.*=String,business\..*\.field=double</li>
<li>includeFullMdc (Optional): Include all fields from the MDC, default false</li>
</ul>
<a name="mdcProfiling"></a> <h2>MDC Profiling</h2>
<p>
MDC Profiling allows to calculate the runtime from request start up to the time until the log message was generated. You must
set one value in the MDC:
<ul>
<li>profiling.requestStart.millis: Time Millis of the Request-Start (Long or String)</li>
</ul>
<p>
Two values are set by the Log Appender:
</p>
<ul>
<li>profiling.requestEnd: End-Time of the Request-End in Date.toString-representation</li>
<li>profiling.requestDuration: Duration of the request (e.g. 205ms, 16sec)</li>
</ul>
The {@link #append(LoggingEvent)} method is thread-safe and may be called by different threads at any time.
@author Mark Paluch
|
getVersion
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j/GelfLogAppender.java
|
MIT
|
public Pattern getPattern() {
return pattern;
}
|
Configuration for dynamic log fields pulled from MDC.
@author Thomas Herzog
|
getPattern
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j2/GelfDynamicMdcFieldType.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j2/GelfDynamicMdcFieldType.java
|
MIT
|
public String getType() {
return type;
}
|
Configuration for dynamic log fields pulled from MDC.
@author Thomas Herzog
|
getType
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j2/GelfDynamicMdcFieldType.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j2/GelfDynamicMdcFieldType.java
|
MIT
|
@PluginFactory
public static GelfDynamicMdcFieldType createField(@PluginAttribute("regex") String regex,
@PluginAttribute("type") String type) {
if (Strings.isEmpty(regex)) {
throw new IllegalArgumentException("Regex is empty");
}
if (Strings.isEmpty(type)) {
throw new IllegalArgumentException("Type is empty");
}
return new GelfDynamicMdcFieldType(Pattern.compile(regex), type);
}
|
Configuration for dynamic log fields pulled from MDC.
@author Thomas Herzog
|
createField
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j2/GelfDynamicMdcFieldType.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j2/GelfDynamicMdcFieldType.java
|
MIT
|
public String getRegex() {
return regex;
}
|
Configuration for dynamic log fields pulled from MDC.
@author Mark Paluch
|
getRegex
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j2/GelfDynamicMdcLogFields.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j2/GelfDynamicMdcLogFields.java
|
MIT
|
@PluginFactory
public static GelfDynamicMdcLogFields createField(@PluginConfiguration final Configuration config,
@PluginAttribute("regex") String regex) {
if (Strings.isEmpty(regex)) {
LOGGER.error("The regex is empty");
return null;
}
return new GelfDynamicMdcLogFields(regex);
}
|
Configuration for dynamic log fields pulled from MDC.
@author Mark Paluch
|
createField
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j2/GelfDynamicMdcLogFields.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j2/GelfDynamicMdcLogFields.java
|
MIT
|
private static void configureFields(MdcGelfMessageAssembler mdcGelfMessageAssembler, GelfLogField[] fields,
GelfDynamicMdcLogFields[] dynamicFieldArray) {
if (fields == null || fields.length == 0) {
mdcGelfMessageAssembler.addFields(LogMessageField.getDefaultMapping(Time, Severity, ThreadName, SourceClassName,
SourceMethodName, SourceLineNumber, SourceSimpleClassName, LoggerName, Marker));
return;
}
for (GelfLogField field : fields) {
if (Strings.isNotEmpty(field.getMdc())) {
mdcGelfMessageAssembler.addField(new MdcMessageField(field.getName(), field.getMdc()));
}
if (Strings.isNotEmpty(field.getLiteral())) {
mdcGelfMessageAssembler.addField(new StaticMessageField(field.getName(), field.getLiteral()));
}
if (field.getPatternLayout() != null) {
mdcGelfMessageAssembler.addField(new PatternLogMessageField(field.getName(), null, field.getPatternLayout()));
}
}
if (dynamicFieldArray != null) {
for (GelfDynamicMdcLogFields gelfDynamicMdcLogFields : dynamicFieldArray) {
mdcGelfMessageAssembler.addField(new DynamicMdcMessageField(gelfDynamicMdcLogFields.getRegex()));
}
}
}
|
Configure fields (literals, MDC, layout).
@param mdcGelfMessageAssembler the assembler
@param fields static field array
@param dynamicFieldArray dynamic field array
|
configureFields
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j2/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j2/GelfLogAppender.java
|
MIT
|
@Override
public void append(LogEvent event) {
if (event == null) {
return;
}
try {
GelfMessage message = createGelfMessage(event);
if (!message.isValid()) {
reportError("GELF Message is invalid: " + message.toJson(), null);
return;
}
if (null == gelfSender || !gelfSender.sendMessage(message)) {
reportError("Could not send GELF message", null);
}
} catch (AppenderLoggingException e) {
throw e;
} catch (Exception e) {
reportError("Could not send GELF message: " + e.getMessage(), e);
}
}
|
Configure fields (literals, MDC, layout).
@param mdcGelfMessageAssembler the assembler
@param fields static field array
@param dynamicFieldArray dynamic field array
|
append
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j2/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j2/GelfLogAppender.java
|
MIT
|
protected GelfMessage createGelfMessage(final LogEvent logEvent) {
return gelfMessageAssembler.createGelfMessage(new Log4j2LogEvent(logEvent));
}
|
Configure fields (literals, MDC, layout).
@param mdcGelfMessageAssembler the assembler
@param fields static field array
@param dynamicFieldArray dynamic field array
|
createGelfMessage
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j2/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j2/GelfLogAppender.java
|
MIT
|
public void reportError(String message, Exception exception) {
errorReporter.reportError(message, exception);
}
|
Configure fields (literals, MDC, layout).
@param mdcGelfMessageAssembler the assembler
@param fields static field array
@param dynamicFieldArray dynamic field array
|
reportError
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j2/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j2/GelfLogAppender.java
|
MIT
|
@Override
protected boolean stop(long timeout, TimeUnit timeUnit, boolean changeLifeCycleState) {
if (null != gelfSender) {
Closer.close(gelfSender);
gelfSender = null;
}
return super.stop(timeout, timeUnit, changeLifeCycleState);
}
|
Configure fields (literals, MDC, layout).
@param mdcGelfMessageAssembler the assembler
@param fields static field array
@param dynamicFieldArray dynamic field array
|
stop
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j2/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j2/GelfLogAppender.java
|
MIT
|
@Override
public void start() {
if (null == gelfSender) {
gelfSender = createGelfSender();
}
super.start();
}
|
Configure fields (literals, MDC, layout).
@param mdcGelfMessageAssembler the assembler
@param fields static field array
@param dynamicFieldArray dynamic field array
|
start
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j2/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j2/GelfLogAppender.java
|
MIT
|
protected GelfSender createGelfSender() {
return GelfSenderFactory.createSender(gelfMessageAssembler, errorReporter, Collections.<String, Object>emptyMap());
}
|
Configure fields (literals, MDC, layout).
@param mdcGelfMessageAssembler the assembler
@param fields static field array
@param dynamicFieldArray dynamic field array
|
createGelfSender
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j2/GelfLogAppender.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j2/GelfLogAppender.java
|
MIT
|
public String getName() {
return name;
}
|
Configuration for a log field.
@author Mark Paluch
|
getName
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j2/GelfLogField.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j2/GelfLogField.java
|
MIT
|
public String getLiteral() {
return literal;
}
|
Configuration for a log field.
@author Mark Paluch
|
getLiteral
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j2/GelfLogField.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j2/GelfLogField.java
|
MIT
|
public String getMdc() {
return mdc;
}
|
Configuration for a log field.
@author Mark Paluch
|
getMdc
|
java
|
mp911de/logstash-gelf
|
src/main/java/biz/paluch/logging/gelf/log4j2/GelfLogField.java
|
https://github.com/mp911de/logstash-gelf/blob/master/src/main/java/biz/paluch/logging/gelf/log4j2/GelfLogField.java
|
MIT
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.