Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Discussion: Separate jenkins logs from the main syslog

未关闭
#4,441 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
38/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
linux

调研方向

检查当前将 Jenkins 条目发送到 syslog 的日志记录设置,并比较 /var/log/jenkins、syslog 和 kern.log。查看 issues 4434 和 4419 中的上下文,并确认进行更改的原因。当 Jenkins 输出在单独的轮换文件中得到处理,且不丢失所需的日志记录或可见性时,即视为完成。

由索引模型根据 Issue 内容生成。

描述

Spotted after identifying https://github.com/nodejs/build/issues/4434

At some point we must have moved the jenkins log files into the syslog. There are files in /var/log/jenkins from August 2022 (Four years ago) but no more and the jenkins information has been put into the syslog where it is fighting for visibility among all the firewall activity (which also goes to kern.log so we have that duplicated). As an example in the last full week of syslog activity we had 1,681,013 entries from jenkins and 25,234,966 from the firewall out of a total of 27,074,871

I would propose that we look at moving it out of the syslog into standalone files which are a bit easier to process when needed. While I appreciate that grep jenkins in the syslog can also work I feel that having it in separate rotated files would just be a bit cleaner.

I had a brief discussion with Richard on this last week but does anyone recall if there was a driving reason for moving towards using the syslog? There's nothing obvious I can see in the issue history in this repository about that change.

Related: https://github.com/nodejs/build/issues/4419

主要语言
Jinja
星标
541
派生
185
平均合并
2 天 18 小时
30 天内合并 PR
6

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

nodejs/build 的其他 Issue

查看 nodejs/build 的全部 Issue

相似的 Issue

更多 DevOps Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。