常见问题汇总 · Issue #I4FMDC · plume开源社区/Plumelog

一、redis在项目中充当什么角色？

redis在项目中两个角色，第一是在redis模式下充当消息队列，第二是项目本身的元数据存储和报警管理

二、为什么我查看redis中有数据，但是后台却查不到呢？

这种情况大概率是server中 plumelog.queue.redis.redisHost 没有配置正确，redis只是充当队列的作用，如果里面能看到数据说明没有server没有消费，正常情况应该是redis是不会积压的

三、为什么我切换redisdb，不起作用？

切换redisdb为了安全考虑，必须设置redis密码，因为日志系统redis推荐独立redis,如果切换了DB代表你的和混合其他redis,plumelog作为日志查询系统，本身不具备高安全，防止redis被攻击，需要设置密码

四、为什么我配置了，之后后台无法查到日志？

排查方法：第一步：停止server,启动日志采集项目，观察redis中有没有数据，如果有说明从项目进入队列是通的，如果没有检查项目端redis配置是否正确；第二步：如果在redis有数据情况，启动server，如果server日志里有ElasticSearch commit! success；表示链路成功

五、为什么我链路追踪里看不到数据？

链路追踪模块产生的日志量比较大，考虑到低需求玩家，默认不集成，需要单独配置，详细查看文档：链路追踪配置

六、plumelog客户端配置能结合配置文件中心使用吗？

肯定是可以的，plumelog配置是配置在三大日志框架的配置文件里面的，可以使用springProperty进行管理配置，具体怎么操作看每个项目自己的情况

七、plumelog目前生产环境已知的已经有多大体量

根据用户反馈，目前搜集到最大的用户每日日志量已经到达3TB，并稳定运行

八、为什么我的项目继承了plumelog就启动就报错？

如果提示redis连接失败，那么说明redis配置错误，如果是其他错误，比如提示类找不到什么情况，应该数据日志配置文件错了，建议先熟练掌握log4j,logback配制文件里面的标签含义

九、应用名称下拉框出不来？

是因为ES请求URL太长了

elasticsearch.yml 里加几个配置

http.max_initial_line_length: "8k"
http.max_header_size: "16k"
http.max_content_length: 500mb

把sql语句写入日志的配置也加到这个上面，好像总看到有人在群里问，并且都好纠结

输入图片说明

Exception in thread "main" java.lang.NoClassDefFoundError: Could not initialize class com.plumelog.core.LogMessageThreadLocal

server服务启动报错了，麻烦看下
org.apache.http.ConnectionClosedException: Connection is closed
at org.elasticsearch.client.RestClient.extractAndWrapCause(RestClient.java:908)
at org.elasticsearch.client.RestClient.performRequest(RestClient.java:299)
at org.elasticsearch.client.RestClient.performRequest(RestClient.java:287)
at com.plumelog.server.client.ElasticLowerClient.getVersion(ElasticLowerClient.java:154)
at com.plumelog.server.client.ClientConfig.initElasticLowerClient(ClientConfig.java:207)
at com.plumelog.server.client.ClientConfig$$EnhancerBySpringCGLIB$$2a617852.CGLIB$initElasticLowerClient$1()
at com.plumelog.server.client.ClientConfig$$EnhancerBySpringCGLIB$$2a617852$$FastClassBySpringCGLIB$$2116c68e.invoke()
at org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:244)
at org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:363)
at com.plumelog.server.client.ClientConfig$$EnhancerBySpringCGLIB$$2a617852.initElasticLowerClient()
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:154)
at org.springframework.beans.factory.support.ConstructorResolver.instantiate(ConstructorResolver.java:622)
at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:456)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1321)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1160)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:555)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:515)
at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:320)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:318)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:199)
at org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(DependencyDescriptor.java:277)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1251)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1171)
at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:593)
at org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:90)
at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessProperties(AutowiredAnnotationBeanPostProcessor.java:374)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1411)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:592)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:515)
at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:320)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:318)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:199)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:845)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:877)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:549)
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:141)
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:743)
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:390)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:312)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1214)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1203)
at com.plumelog.server.LogServerStart.main(LogServerStart.java:24)

为什么我启动plumelog-server，访问页面是springbootadmin，不是plumelog的登录页

spring.boot.admin.context-path=admin 这个配置被你漏了吧

ui页面，链路追踪，查询tarceId，报错：
{"error":{"root_cause":[{"type":"query_shard_exception","reason":"No mapping found for [time] in order to sort on","index_uuid":"9-L9MlmpQymuSOjPmcaLCA","index":"plume_log_trace_20220729"}],
"type":"search_phase_execution_exception",
"reason":"all shards failed","phase":"query","grouped":true,"failed_shards":[{"shard":0,"index":"plume_log_trace_20220729","node":"r-ZSxGK5QeqL-NTFNhB8mQ",
"reason":{"type":"query_shard_exception","reason":"No mapping found for [time] in order to sort on","index_uuid":"9-L9MlmpQymuSOjPmcaLCA","index":"plume_log_trace_20220729"}}]},"status":400}
，我看了es里面索引的结构，没有"time"这个字段，应该是bug
输入图片说明

是应为你这个索引没有值，你的链路数据为空

输入图片说明
我引入了3.5.2版本的plumelog-lite-spring-boot-starter，然后配置了 log4j2.xml 文件但在项目启动的时候会报错，这个要怎么解决呢？
2022-10-26 14:39:09,062 main ERROR appenders contains an invalid element or attribute "Appender"
2022-10-26 14:39:09,077 main ERROR Unable to locate appender "plumelog" for logger config "root"
2022-10-26 14:39:09,792 main ERROR appenders contains an invalid element or attribute "Appender"
2022-10-26 14:39:09,794 main ERROR Unable to locate appender "plumelog" for logger config "root"

你把logback的配置贴到log4j2里面干嘛，当然会报错，另外lite暂时只支持logback

我这边根据lite版的配置，打开界面后，没有日志信息，请问是什么原因

输入图片说明

输入图片说明
前期日志显示正常，现在查不出任何数据，滚动日志可以正常显示。服务重启也没有用，redis显示连接正常。

这个问题解决了吗?

同问 +1

解决了吗

Description:

Parameter 0 of constructor in com.github.xiaoymin.knife4j.spring.plugin.DynamicResponseModelReader required a bean of type 'springfox.documentation.schema.TypeNameExtractor' that could not be found.

Action:

Consider defining a bean of type 'springfox.documentation.schema.TypeNameExtractor' in your configuration.

GVP plume开源社区 / Plumelog

内容风险标识

常见问题汇总置顶

评论 (19)

GVPplume开源社区 / Plumelog

内容风险标识

常见问题汇总 置顶

评论 (19)

搜索帮助

GVP plume开源社区 / Plumelog

常见问题汇总置顶