Skip to content

Conversation

@iceBear67
Copy link

@iceBear67 iceBear67 commented Aug 25, 2025

Background

有的时候我想在 journal 里面看每个连接的分流情况,但是大鹅一直在刷节点测速日志以及存活状态,使得我基本上看不到有价值的信息,因此我将相关测速日志的 log level 改为了 debug。

我想可能有其他人也遇到过类似的问题,因此提交此 PR.

没有在项目里见到 CONTRIBUTING.md, 因此如果有做的不对的地方烦请指出, 谢谢!

Checklist

  • The Pull Request has been fully tested
  • There's an entry in the CHANGELOGS
    It's not a new version so I didn't change that.
  • There is a user-facing docs PR against https://github.com/daeuniverse/dae
    It's integrated into this PR. if this is inappropirate, I'll submit another PR later.

Full Changelogs

  • 更改了 alive_dialer_set.go 中打印延迟及节点列表时使用的 log level.

Issue Reference

I haven't seen any.

Test Result

It works on my machine.

@iceBear67 iceBear67 requested review from a team as code owners August 25, 2025 09:12
@dae-prow dae-prow bot added the chore label Aug 25, 2025
@LostAttractor
Copy link
Contributor

LostAttractor commented Aug 25, 2025

个人认为节点状态变更相关的日志应当是高优先级的,但的确现在过滤流量相关的日志较为困难

@ppdragon16
Copy link
Contributor

ppdragon16 commented Aug 26, 2025

+1. 对我来说(四个机场的节点混合选择),"节点测速日志以及存活状态"就是"有价值的信息"。

可以自己写简单的脚本来监听并分析log,比如dns统计等。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants