[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2024-12-22。"],[[["Java's default `STDOUT` and `STDERR` outputs are sent to Cloud Logging, but they lack granular log severity levels, thus requiring the Java Logging API (JUL) for proper severity propagation."],["Alternative logging frameworks like SLF4J, Log4j 2, and Apache Commons Logging can be integrated by formatting logs in JSON for severity propagation or by using a bridge/adapter to send logs to the Java Logging API."],["Spring Cloud Run functions can leverage Spring Cloud's Google Cloud Logging Starter and `CONSOLE_JSON` appender to format and output logs in JSON, compatible with Cloud Logging, and it can also route SLF4J logs to the Java Logging API."],["Ensure removal of bridges, such as `jul-to-slf4j`, or Log4j JDK Logging Adapter, that may interfere with correct log formatting and severity level propagation when using the Java Logging API."],["Logging frameworks such as Logback and Log4j 2, that dont directly route to Java Logging API, can route first to SLF4J which can then use the Java Logging API implementation for correct log messaging and severity."]]],[]]
