Spring Cloud Stackdriver记录通过控制台登录

2024-01-10 16:00 更新

对于Logback，org/springframework/cloud/gcp/autoconfigure/logging/logback-json-appender.xml文件可用于导入，以使其更易于配置JSON Logback附加程序。

然后，您的配置可能如下所示：

<configuration>
  <include resource="org/springframework/cloud/gcp/autoconfigure/logging/logback-json-appender.xml" />

  <root level="INFO">
    <appender-ref ref="CONSOLE_JSON" />
  </root>
</configuration>

如果您的应用程序在Google Kubernetes Engine，Google Compute Engine或Google App Engine Flexible上运行，则您的控制台日志将自动保存到Google Stackdriver Logging。因此，您只需在日志记录配置中包含org/springframework/cloud/gcp/autoconfigure/logging/logback-json-appender.xml，即可将JSON条目记录到控制台。跟踪ID将正确设置。

如果要对日志输出进行更多控制，则可以进一步配置附加程序。可以使用以下属性：

Property	默认值	描述
`projectId`	If not set, default value is determined in the following order: `SPRING_CLOUD_GCP_LOGGING_PROJECT_ID` Environmental Variable. Value of `DefaultGcpProjectIdProvider.getProjectId()`	This is used to generate fully qualified Stackdriver Trace ID format: `projects/[PROJECT-ID]/traces/[TRACE-ID]`. This format is required to correlate trace between Stackdriver Trace and Stackdriver Logging. If `projectId` is not set and cannot be determined, then it’ll log `traceId` without the fully qualified format.
`includeTraceId`	`true`	Should the `traceId` be included
`includeSpanId`	`true`	Should the `spanId` be included
`includeLevel`	`true`	Should the severity be included
`includeThreadName`	`true`	Should the thread name be included
`includeMDC`	`true`	Should all MDC properties be included. The MDC properties `X-B3-TraceId`, `X-B3-SpanId` and `X-Span-Export` provided by Spring Sleuth will get excluded as they get handled separately
`includeLoggerName`	`true`	Should the name of the logger be included
`includeFormattedMessage`	`true`	Should the formatted log message be included.
`includeExceptionInMessage`	`true`	Should the stacktrace be appended to the formatted log message. This setting is only evaluated if `includeFormattedMessage` is `true`
`includeContextName`	`true`	Should the logging context be included
`includeMessage`	`false`	Should the log message with blank placeholders be included
`includeException`	`false`	Should the stacktrace be included as a own field

这是这种Logback配置的示例：

<configuration >
  <property name="projectId" value="${projectId:-${GOOGLE_CLOUD_PROJECT}}"/>

  <appender name="CONSOLE_JSON" class="ch.qos.logback.core.ConsoleAppender">
    <encoder class="ch.qos.logback.core.encoder.LayoutWrappingEncoder">
      <layout class="org.springframework.cloud.gcp.logging.StackdriverJsonLayout">
        <projectId>${projectId}</projectId>

        <!--<includeTraceId>true</includeTraceId>-->
        <!--<includeSpanId>true</includeSpanId>-->
        <!--<includeLevel>true</includeLevel>-->
        <!--<includeThreadName>true</includeThreadName>-->
        <!--<includeMDC>true</includeMDC>-->
        <!--<includeLoggerName>true</includeLoggerName>-->
        <!--<includeFormattedMessage>true</includeFormattedMessage>-->
        <!--<includeExceptionInMessage>true</includeExceptionInMessage>-->
        <!--<includeContextName>true</includeContextName>-->
        <!--<includeMessage>false</includeMessage>-->
        <!--<includeException>false</includeException>-->
      </layout>
    </encoder>
  </appender>
</configuration>

以上内容是否对您有帮助：

← Spring Cloud Stackdriver记录通过API记录

Spring Cloud Stackdriver记录示例 →

写笔记

我要补充

Spring Cloud Stackdriver记录 通过控制台登录

推荐文章

推荐教程

推荐课程

Spring Cloud Stackdriver记录通过控制台登录