Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

应用日志收集、存储与推送机制优化 #371

Closed
barnettZQG opened this issue Aug 22, 2019 · 0 comments
Closed

应用日志收集、存储与推送机制优化 #371

barnettZQG opened this issue Aug 22, 2019 · 0 comments
Assignees
Labels
Milestone

Comments

@barnettZQG
Copy link
Collaborator

@barnettZQG barnettZQG commented Aug 22, 2019

已知缺陷:

  1. 应用日志收集存在丢失日志文件故障,默认情况下Rainbond设置的docker日志驱动配置为最大生成两个日志文件,当容器日志文件达到最大值切换写以后,Rainbond日志收集器死锁。
  2. 应用日志在管理节点的存储落盘时为了减小磁盘IO的操作频率,采用了缓存写的模式,每产生512条日志或已持续两分钟未落盘时强制落盘持久化。
  3. 前端推送日志时采用的是进入日志页面后建立websocket请求来获取日志流。当服务异常启动时,部分服务只会产生很少的日志则已退出,前端用户侧可能还未建立日志推送链路。因此用户无法第一时间获取到关键日志。

5.1.7 版本中做以下优化:

  1. 解决上诉问题1,增加重试机制防止出现部分容器日志停止收集问题。
  2. 减小日志落盘时间间隔和条数,尽可能加快日志落盘。
  3. 重构前端websoket推送机制,采用长链接websocket机制来推送服务的各类消息包含日志。尽可能准确实时的将服务日志推送到前端。
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.