feat:集成elk

master
Wang XinLong 2024-05-20 21:39:49 +08:00
parent f8ad6e717b
commit 50de030590
6 changed files with 95 additions and 80 deletions

View File

@ -89,3 +89,33 @@
2024-05-19 17:01:08.734 |  INFO 28160 | main [TID:N/A] c.a.c.n.refresh.NacosContextRefresher  | [Nacos Config] Listening config: dataId=muyu-auth-dev.yml, group=DEFAULT_GROUP
2024-05-19 17:01:08.738 |  INFO 28160 | main [TID:N/A] c.a.c.n.refresh.NacosContextRefresher  | [Nacos Config] Listening config: dataId=muyu-auth, group=DEFAULT_GROUP
2024-05-19 17:01:08.738 |  INFO 28160 | main [TID:N/A] c.a.c.n.refresh.NacosContextRefresher  | [Nacos Config] Listening config: dataId=muyu-auth.yml, group=DEFAULT_GROUP
2024-05-19 21:16:49.289 |  WARN 28160 | Thread-3 [TID:N/A] c.a.n.common.http.HttpClientBeanHolder  | [HttpClientBeanHolder] Start destroying common HttpClient
2024-05-19 21:16:49.289 |  WARN 28160 | Thread-10 [TID:N/A] c.a.nacos.common.notify.NotifyCenter  | [NotifyCenter] Start destroying Publisher
2024-05-19 21:16:49.289 |  WARN 28160 | Thread-10 [TID:N/A] c.a.nacos.common.notify.NotifyCenter  | [NotifyCenter] Destruction of the end
2024-05-19 21:16:49.291 |  WARN 28160 | Thread-3 [TID:N/A] c.a.n.common.http.HttpClientBeanHolder  | [HttpClientBeanHolder] Destruction of the end
2024-05-19 21:16:49.335 |  INFO 28160 | SpringApplicationShutdownHook [TID:N/A] c.a.c.n.registry.NacosServiceRegistry  | De-registering from Nacos Server now...
2024-05-19 21:16:49.378 |  INFO 28160 | SpringApplicationShutdownHook [TID:N/A] c.a.c.n.registry.NacosServiceRegistry  | De-registration finished.
2024-05-19 21:17:02.149 |  INFO 20580 | main [TID: N/A] c.a.n.client.env.SearchableProperties  | properties search order:PROPERTIES->JVM->ENV->DEFAULT_SETTING
2024-05-19 21:17:02.935 |  INFO 20580 | main [TID: N/A] c.a.n.p.a.s.c.ClientAuthPluginManager  | [ClientAuthPluginManager] Load ClientAuthService com.alibaba.nacos.client.auth.impl.NacosClientAuthServiceImpl success.
2024-05-19 21:17:02.935 |  INFO 20580 | main [TID: N/A] c.a.n.p.a.s.c.ClientAuthPluginManager  | [ClientAuthPluginManager] Load ClientAuthService com.alibaba.nacos.client.auth.ram.RamClientAuthServiceImpl success.
2024-05-19 21:17:07.952 |  WARN 20580 | main [TID: N/A] c.a.c.n.c.NacosPropertySourceBuilder  | Ignore the empty nacos configuration and get it based on dataId[muyu-auth] & group[DEFAULT_GROUP]
2024-05-19 21:17:08.009 |  WARN 20580 | main [TID: N/A] c.a.c.n.c.NacosPropertySourceBuilder  | Ignore the empty nacos configuration and get it based on dataId[muyu-auth.yml] & group[DEFAULT_GROUP]
2024-05-19 21:17:08.055 |  INFO 20580 | main [TID: N/A] com.muyu.auth.MuYuAuthApplication  | The following 1 profile is active: "dev"
2024-05-19 21:17:11.455 |  INFO 20580 | main [TID: N/A] o.apache.catalina.core.StandardService  | Starting service [Tomcat]
2024-05-19 21:17:11.455 |  INFO 20580 | main [TID: N/A] org.apache.catalina.core.StandardEngine  | Starting Servlet engine: [Apache Tomcat/9.0.76]
2024-05-19 21:17:11.619 |  INFO 20580 | main [TID: N/A] o.a.c.c.C.[Tomcat].[localhost].[/]  | Initializing Spring embedded WebApplicationContext
2024-05-19 21:17:13.799 |  INFO 20580 | main [TID: N/A] c.a.c.sentinel.SentinelWebMvcConfigurer  | [Sentinel Starter] register SentinelWebInterceptor with urlPatterns: [/**].
2024-05-19 21:17:16.868 |  WARN 20580 | main [TID: N/A] iguration$LoadBalancerCaffeineWarnLogger | Spring Cloud LoadBalancer is currently working with the default cache. While this cache implementation is useful for development and tests, it's recommended to use Caffeine cache in production.You can switch to using Caffeine cache, by adding it and org.springframework.cache.caffeine.CaffeineCacheManager to the classpath.
2024-05-19 21:17:17.006 |  INFO 20580 | main [TID: N/A] c.a.n.p.a.s.c.ClientAuthPluginManager  | [ClientAuthPluginManager] Load ClientAuthService com.alibaba.nacos.client.auth.impl.NacosClientAuthServiceImpl success.
2024-05-19 21:17:17.006 |  INFO 20580 | main [TID: N/A] c.a.n.p.a.s.c.ClientAuthPluginManager  | [ClientAuthPluginManager] Load ClientAuthService com.alibaba.nacos.client.auth.ram.RamClientAuthServiceImpl success.
2024-05-19 21:17:17.288 |  INFO 20580 | main [TID: N/A] c.a.c.n.registry.NacosServiceRegistry  | nacos registry, DEFAULT_GROUP muyu-auth 192.168.157.1:9200 register finished
2024-05-19 21:17:18.478 |  INFO 20580 | main [TID: N/A] com.muyu.auth.MuYuAuthApplication  | Started MuYuAuthApplication in 18.167 seconds (JVM running for 26.683)
2024-05-19 21:17:18.495 |  INFO 20580 | main [TID: N/A] c.a.c.n.refresh.NacosContextRefresher  | [Nacos Config] Listening config: dataId=muyu-auth-dev.yml, group=DEFAULT_GROUP
2024-05-19 21:17:18.495 |  INFO 20580 | main [TID: N/A] c.a.c.n.refresh.NacosContextRefresher  | [Nacos Config] Listening config: dataId=muyu-auth, group=DEFAULT_GROUP
2024-05-19 21:17:18.495 |  INFO 20580 | main [TID: N/A] c.a.c.n.refresh.NacosContextRefresher  | [Nacos Config] Listening config: dataId=muyu-auth.yml, group=DEFAULT_GROUP
2024-05-19 21:21:44.570 |  WARN 20580 | Thread-3 [TID: N/A] c.a.n.common.http.HttpClientBeanHolder  | [HttpClientBeanHolder] Start destroying common HttpClient
2024-05-19 21:21:44.570 |  WARN 20580 | Thread-10 [TID: N/A] c.a.nacos.common.notify.NotifyCenter  | [NotifyCenter] Start destroying Publisher
2024-05-19 21:21:44.570 |  WARN 20580 | Thread-10 [TID: N/A] c.a.nacos.common.notify.NotifyCenter  | [NotifyCenter] Destruction of the end
2024-05-19 21:21:44.571 |  WARN 20580 | Thread-3 [TID: N/A] c.a.n.common.http.HttpClientBeanHolder  | [HttpClientBeanHolder] Destruction of the end
2024-05-19 21:21:44.601 |  INFO 20580 | SpringApplicationShutdownHook [TID: N/A] c.a.c.n.registry.NacosServiceRegistry  | De-registering from Nacos Server now...
2024-05-19 21:21:44.667 |  INFO 20580 | SpringApplicationShutdownHook [TID: N/A] c.a.c.n.registry.NacosServiceRegistry  | De-registration finished.

View File

@ -66,83 +66,4 @@
<appender-ref ref="console"/>
</root>
<!--系统操作日志-->
<root level="info">
<appender-ref ref="file_info"/>
<appender-ref ref="file_error"/>
</root>
<!-- 引用 Spring Boot 的 logback 基础配置 -->
<include resource="org/springframework/boot/logging/logback/defaults.xml" />
<!-- 变量 yudao.info.base-package基础业务包 -->
<springProperty scope="context" name="kirin.info.base-package" source="kirin.info.base-package"/>
<!-- 格式化输出:%d 表示日期,%X{tid} SkWalking 链路追踪编号,%thread 表示线程名,%-5level级别从左显示 5 个字符宽度,%msg日志消息%n是换行符 -->
<property name="PATTERN_DEFAULT" value="%d{${LOG_DATEFORMAT_PATTERN:-yyyy-MM-dd HH:mm:ss.SSS}} | %highlight(${LOG_LEVEL_PATTERN:-%5p} ${PID:- }) | %boldYellow(%thread [%tid]) %boldGreen(%-40.40logger{39}) | %m%n${LOG_EXCEPTION_CONVERSION_WORD:-%wEx}"/>
<!-- 控制台 Appender -->
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">     
<encoder class="ch.qos.logback.core.encoder.LayoutWrappingEncoder">
<layout class="org.apache.skywalking.apm.toolkit.log.logback.v1.x.TraceIdPatternLogbackLayout">
<pattern>${PATTERN_DEFAULT}</pattern>
</layout>
</encoder>
</appender>
<!-- 文件 Appender -->
<!-- 参考 Spring Boot 的 file-appender.xml 编写 -->
<appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
<encoder class="ch.qos.logback.core.encoder.LayoutWrappingEncoder">
<layout class="org.apache.skywalking.apm.toolkit.log.logback.v1.x.TraceIdPatternLogbackLayout">
<pattern>${PATTERN_DEFAULT}</pattern>
</layout>
</encoder>
<!-- 日志文件名 -->
<file>${LOG_FILE}</file>
<rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy">
<!-- 滚动后的日志文件名 -->
<fileNamePattern>${LOGBACK_ROLLINGPOLICY_FILE_NAME_PATTERN:-${LOG_FILE}.%d{yyyy-MM-dd}.%i.gz}</fileNamePattern>
<!-- 启动服务时,是否清理历史日志,一般不建议清理 -->
<cleanHistoryOnStart>${LOGBACK_ROLLINGPOLICY_CLEAN_HISTORY_ON_START:-false}</cleanHistoryOnStart>
<!-- 日志文件,到达多少容量,进行滚动 -->
<maxFileSize>${LOGBACK_ROLLINGPOLICY_MAX_FILE_SIZE:-10MB}</maxFileSize>
<!-- 日志文件的总大小0 表示不限制 -->
<totalSizeCap>${LOGBACK_ROLLINGPOLICY_TOTAL_SIZE_CAP:-0}</totalSizeCap>
<!-- 日志文件的保留天数 -->
<maxHistory>${LOGBACK_ROLLINGPOLICY_MAX_HISTORY:-30}</maxHistory>
</rollingPolicy>
</appender>
<!-- 异步写入日志,提升性能 -->
<appender name="ASYNC" class="ch.qos.logback.classic.AsyncAppender">
<!-- 不丢失日志。默认的,如果队列的 80% 已满,则会丢弃 TRACT、DEBUG、INFO 级别的日志 -->
<discardingThreshold>0</discardingThreshold>
<!-- 更改默认的队列的深度,该值会影响性能。默认值为 256 -->
<queueSize>256</queueSize>
<appender-ref ref="FILE"/>
</appender>
<!-- SkyWalking GRPC 日志收集实现日志中心。注意SkyWalking 8.4.0 版本开始支持 -->
<appender name="GRPC" class="org.apache.skywalking.apm.toolkit.log.logback.v1.x.log.GRPCLogClientAppender">
<encoder class="ch.qos.logback.core.encoder.LayoutWrappingEncoder">
<layout class="org.apache.skywalking.apm.toolkit.log.logback.v1.x.TraceIdPatternLogbackLayout">
<pattern>${PATTERN_DEFAULT}</pattern>
</layout>
</encoder>
</appender>
<!-- 本地环境 -->
<springProfile name="local">
<root level="INFO">
<appender-ref ref="STDOUT"/>
<appender-ref ref="GRPC"/> <!-- 本地环境下,如果不想接入 SkyWalking 日志服务,可以注释掉本行 -->
<appender-ref ref="ASYNC"/> <!-- 本地环境下,如果不想打印日志,可以注释掉本行 -->
</root>
</springProfile>
<!-- 其它环境 -->
<springProfile name="dev,test,stage,prod,default">
<root level="INFO">
<appender-ref ref="STDOUT"/>
<appender-ref ref="ASYNC"/>
<appender-ref ref="GRPC"/>
</root>
</springProfile>
</configuration>

View File

@ -18,6 +18,13 @@
</properties>
<dependencies>
<dependency>
<groupId>net.logstash.logback</groupId>
<artifactId>logstash-logback-encoder</artifactId>
<version>6.6</version>
</dependency>
<!-- SpringCloud Alibaba Nacos -->
<dependency>
<groupId>com.alibaba.cloud</groupId>

View File

@ -1,7 +1,6 @@
package com.muyu.source.controller;
import java.sql.SQLException;
import java.util.HashMap;
import java.util.List;
import javax.servlet.http.HttpServletResponse;

View File

@ -28,3 +28,4 @@ spring:
logging:
level:
com.muyu.system.mapper: DEBUG
config: classpath:logback-spring.xml

View File

@ -0,0 +1,57 @@
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<include resource="org/springframework/boot/logging/logback/base.xml" />
<springProperty scope="context" name="springAppName" source="Website may be available for web development ideas"/>
<springProperty scope="context" name="serverPort" source="server.port"/>
<appender name="LOGSTASH" class="net.logstash.logback.appender.LogstashTcpSocketAppender">
<!--logstash的服务地址和端口可以实际情况设置-->
<destination>192.168.23.130:5044</destination>
<!-- 日志输出编码 -->
<encoder charset="UTF-8" class="net.logstash.logback.encoder.LogstashEncoder">
<providers>
<timestamp>
<timeZone>UTC</timeZone>
</timestamp>
<pattern>
<pattern>
{
<!--应用名称 -->
"app": "${springAppName}_${serverPort}",
<!--打印时间 -->
"timestamp": "%d{yyyy-MM-dd HH:mm:ss.SSS}",
<!--线程名称 -->
"thread": "%thread",
<!--日志级别 -->
"level": "%level",
<!--日志名称 -->
"logger_name": "%logger",
<!--日志信息 -->
"message": "%msg",
<!--日志堆栈 -->
"stack_trace": "%exception"
}
</pattern>
</pattern>
</providers>
</encoder>
</appender>
<!--定义日志文件的存储地址,使用绝对路径-->
<property name="LOG_HOME" value="/Users/jianchenghou/log/elklog"/>
<!-- 按照每天生成日志文件 -->
<appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
<rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
<!--日志文件输出的文件名-->
<fileNamePattern>${LOG_HOME}/${springAppName}-${serverPort}-%d{yyyy-MM-dd}.log</fileNamePattern>
</rollingPolicy>
<encoder>
<pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</pattern>
</encoder>
</appender>
<root level="INFO">
<appender-ref ref="LOGSTASH" />
<appender-ref ref="FILE" />
<appender-ref ref="CONSOLE" />
</root>
</configuration>