-
Notifications
You must be signed in to change notification settings - Fork 101
-
Notifications
You must be signed in to change notification settings - Fork 101
JBoss AS7 logging - Disable MessageParam# splitting. #87
Comments
How about a Pull-Request? |
@djmoky83 You can always filter out the MessageParam fields using logstash
|
Hi @birnbuazn, That's correct what you said above but sometimes number format exception/other kind of exceptions occur in the ELK logs because of that. It would be avoidable if there is a configuration to disable all message params. |
@sohilpatel These exceptions only occur within ElasticSearch, if you do not filter out the fields. Whether you do that within the GELF logger or within Logstash is irrelevant. |
Hi @birnbuazn, Yes you are correct. I updated my filter configuration properly and exception disappeared. Thanks for that. :) |
Java.util.logging-based log handlers can be now configured whether to include log message parameters in the GELF message with includeLogMessageParameters=true/false, defaults to true. Log event message parameters are usually used together with message bundles: logger.log(Level.INFO, "my.message.key", new Object[] { "hello", "my", "world" });
That's implemented now with 10eae2f. |
Using JBoss AS7 logging handler, will split params in the message to "MessageParam#={value}"
Please have a configuration to disable this.
The text was updated successfully, but these errors were encountered: