Appender default flushlevel is inconsistent with java-logging client's default #1328
Assignees
Labels
api: logging
Issues related to the googleapis/java-logging-logback API.
priority: p3
Desirable enhancement or fix. May not be included in next release.
Comments
product-auto-label
bot
added
the
api: logging
cindy-peng
added
the
priority: p3
|
Good catch! Thanks for reporting @burkedavison! We will work on a fix here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The java-logging library updated its flushlevel default to
OFFin Dec 2018 due to the performance cost of flushing on the same thread as the application.However, the java-logging-logback appender was implemented in May 2017 to default to
ERROR, and continues to default toERROR.( Add'l context: This came to our attention with a request to make Spring Cloud GCP's helper-implementation of a logback appender match the base library's default. See GoogleCloudPlatform/spring-cloud-gcp#2906 for discussion. )
The text was updated successfully, but these errors were encountered: