Bertrand Renuart

Consider the following sample encoder configuration: ``` fields level /level ``` This configuration produces output like this (pretty printed for convenience): ``` { "fields": { "level": "INFO" } } ```...

See https://github.com/logfellow/logstash-logback-encoder/discussions/723 for areas that need clarification.

Project should be validated against the upcoming `logback:1.3.0`.

The `#asLong` and `#asDouble` operations should trim the input value before attempting to convert the string into a value of the desired type.

Rules: - Property must be validated eagerly by the corresponding setter method. An IllegalArgumentException should be thrown when the validation fails. A NullPointerException is currently thrown in most cases for...

Deprecate support for Logback Layout

2

Logback has deprecated the use of `Layout` in favour of `Encoder`. A `LayoutWrappingEncoder` adapter is provided to bridge between the two. Logback `OutputStreamAppender` and sub-classes like `ConsoleAppender` still accept a...

Clarify threadNameFormat (and possibly add some words about it in the documentation)

2

Both the `AsyncDisruptorAppender` and `LogstashTcpSocketAppender` appenders allow for the customisation of the name of their processing threads. This customisation is done via a standard Java format pattern set via the...

LogstachTcpSocketAppender: collect metrics

2

Would be nice to collect metrics about the appender usage/behaviour: - sending rates - drop rates - total number of TCP connections created - total number of connection failure -...

RefreshScope dispose beans in unpredictable order

4

This issue was discovered while investigating https://github.com/spring-cloud/spring-cloud-netflix/issues/3174#issuecomment-419349960. To summarise the original tread: When disposed, `RefreshScope` starts by clearing its local cache of target beans then proceeds with their disposal. A...

LogstashEncoder does not accept additional encoder besides the predefined ones. If user tries to add an extra encoder using the `` configuration element, it logs an ERROR status indicating this...