我当前部署的当前Logback配置如下(您可以说我的构想已耗尽...)：

%-4relative [%thread] %-5level %logger{35} - %msg

application.log

WARN

tech.provingground.dive_overwatch.etc.logging.enhancers.TestEnhancer

%-4relative [%thread] %-5level %logger{35} - %msg

查看应用程序中的标准，我可以看到许多日志行指向来自Stackdriver的拒绝请求：

java.lang.RuntimeException: java.util.concurrent.TimeoutException: Waited 6 seconds for com.google.common.util.concurrent.CollectionFuture$ListFuture@77fbc3ba[status=PENDING, info=[futures=[[com.google.api.core.ApiFutureToListenableFuture@772ddfb8, com.google.api.core.ApiFutureToListenableFuture@7d905614, com.google.api.core.ApiFutureToListenableFuture@7396512d, com.google.api.core.ApiFutureToListenableFuture@5ad9baf6]]]]

at com.google.cloud.logging.LoggingImpl.flush(LoggingImpl.java:581)

at com.google.cloud.logging.LoggingImpl.write(LoggingImpl.java:562)

at com.google.cloud.logging.logback.LoggingAppender.append(LoggingAppender.java:215)

at com.google.cloud.logging.logback.LoggingAppender.append(LoggingAppender.java:70)

at ch.qos.logback.core.UnsynchronizedAppenderBase.doAppend(UnsynchronizedAppenderBase.java:84)

[...]如果是身份验证错误，我可以理解403或类似的状态码，但是标准环境应该提供服务帐户，并自动授予

Logs Writer