Reduce log spam of vMCP pod by logging cache sync messages at debug

未关闭适合新手

#7,109 创建于 2026年11月11日 0 条评论 0 个 reaction 已指派 0 人在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度: 2/5
预计耗时: 1-3 小时
新手友好度: 76/100

Issue 类型: 缺陷
描述清晰度: 描述清楚
活跃度: 活跃
技术栈: go, kubernetes
领域: observability

调研方向

找到输出“waiting for Kubernetes cache sync”和“kubernetes cache synced successfully”的 vMCP pod 代码。阅读周围的 logging 调用，并检查项目如何设置 log level。将这些重复的 cache sync 消息改为 debug level；完成的标准是它们不再以 info level 出现。

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

描述

kubernetes needs-triage

At info log level, there are 40 messages / minute just repeating that the cache is being waited on, and then it's successful. I don't think these repetitious messages warrant being at that log level and should be reduced in priority in order to make the logs easier to parse.

Example of what I'm seeing

{"time":"2026-11-10T21:21:49Z","level":"INFO","msg":"kubernetes cache synced successfully"}
{"time":"2026-11-10T21:21:54Z","level":"INFO","msg":"waiting for Kubernetes cache sync"}
{"time":"2026-11-10T21:21:54Z","level":"INFO","msg":"kubernetes cache synced successfully"}
{"time":"2026-11-10T21:21:59Z","level":"INFO","msg":"waiting for Kubernetes cache sync"}
{"time":"2026-11-10T21:21:59Z","level":"INFO","msg":"kubernetes cache synced successfully"}
{"time":"2026-11-10T21:22:04Z","level":"INFO","msg":"waiting for Kubernetes cache sync"}
{"time":"2026-11-10T21:22:04Z","level":"INFO","msg":"kubernetes cache synced successfully"}
{"time":"2026-11-10T21:22:09Z","level":"INFO","msg":"waiting for Kubernetes cache sync"}
{"time":"2026-11-10T21:22:09Z","level":"INFO","msg":"kubernetes cache synced successfully"}
{"time":"2026-11-10T21:22:14Z","level":"INFO","msg":"waiting for Kubernetes cache sync"}
{"time":"2026-11-10T21:22:14Z","level":"INFO","msg":"kubernetes cache synced successfully"}
{"time":"2026-11-10T21:22:19Z","level":"INFO","msg":"waiting for Kubernetes cache sync"}
{"time":"2026-11-10T21:22:19Z","level":"INFO","msg":"kubernetes cache synced successfully"}
{"time":"2026-11-10T21:22:24Z","level":"INFO","msg":"waiting for Kubernetes cache sync"}
{"time":"2026-11-10T21:22:24Z","level":"INFO","msg":"kubernetes cache synced successfully"}
{"time":"2026-11-10T21:22:29Z","level":"INFO","msg":"waiting for Kubernetes cache sync"}
{"time":"2026-11-10T21:22:29Z","level":"INFO","msg":"kubernetes cache synced successfully"}
{"time":"2026-11-10T21:22:34Z","level":"INFO","msg":"waiting for Kubernetes cache sync"}
{"time":"2026-11-10T21:22:34Z","level":"INFO","msg":"kubernetes cache synced successfully"}
{"time":"2026-11-10T21:22:39Z","level":"INFO","msg":"waiting for Kubernetes cache sync"}
{"time":"2026-11-10T21:22:39Z","level":"INFO","msg":"kubernetes cache synced successfully"}
{"time":"2026-11-10T21:22:44Z","level":"INFO","msg":"waiting for Kubernetes cache sync"}
{"time":"2026-11-10T21:22:44Z","level":"INFO","msg":"kubernetes cache synced successfully"}
{"time":"2026-11-10T21:22:49Z","level":"INFO","msg":"waiting for Kubernetes cache sync"}
{"time":"2026-11-10T21:22:49Z","level":"INFO","msg":"kubernetes cache synced successfully"}
{"time":"2026-11-10T21:22:54Z","level":"INFO","msg":"waiting for Kubernetes cache sync"}
{"time":"2026-11-10T21:22:54Z","level":"INFO","msg":"kubernetes cache synced successfully"}
{"time":"2026-11-10T21:22:59Z","level":"INFO","msg":"waiting for Kubernetes cache sync"}
{"time":"2026-11-10T21:22:59Z","level":"INFO","msg":"kubernetes cache synced successfully"}
{"time":"2026-11-10T21:23:04Z","level":"INFO","msg":"waiting for Kubernetes cache sync"}
{"time":"2026-11-10T21:23:04Z","level":"INFO","msg":"kubernetes cache synced successfully"}
{"time":"2026-11-10T21:23:09Z","level":"INFO","msg":"waiting for Kubernetes cache sync"}
{"time":"2026-11-10T21:23:09Z","level":"INFO","msg":"kubernetes cache synced successfully"}
{"time":"2026-11-10T21:23:14Z","level":"INFO","msg":"waiting for Kubernetes cache sync"}
{"time":"2026-11-10T21:23:14Z","level":"INFO","msg":"kubernetes cache synced successfully"}
{"time":"2026-11-10T21:23:19Z","level":"INFO","msg":"waiting for Kubernetes cache sync"}

主要语言: Go
星标: 2.3k
派生: 326
平均合并: 22 小时 47 分钟
30 天内合并 PR: 162

环境准备

没有 Dockerfile 或 Docker Compose 文件
有 Pull Request 模板
阅读贡献指南

从这里开始

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

stacklok/toolhive 的其他 Issue

Filter vMCP tools/list with tool:read, as the single-server path does
未关闭
- 哪里不对？
难度 2/5 1-3 小时新手友好度 65/100

stacklok/toolhive#6925 · 1 条评论 · 2026年10月22日创建

维护者通常 1 天内回复
proxyrunner tool-filter middleware strips SEP-2322 Modern envelope from tools/list, breaking vMCP health checks
可能重新可做 @alex-feel 于 47 天前认领，目前没有进行中的 PR。未关闭
- 哪里不对？
难度 2/5 1-3 小时新手友好度 82/100

stacklok/toolhive#6684 · 5 条评论 · 1 个 reaction · 已指派 1 人 · 2026年9月18日创建

维护者通常 1 天内回复
HttpClientBuilder.Build() ignores HTTP(S)_PROXY (auth-server OAuth/DCR calls bypass forward proxy)
可能已有人在做 @schonmann 于 37 天前认领。未关闭
- 哪里不对？
难度 2/5 1-3 小时新手友好度 78/100

stacklok/toolhive#6671 · 2 条评论 · 1 个 reaction · 已指派 1 人 · 2026年9月16日创建

维护者通常 1 天内回复
Delete the dead pkg/vmcp/server/adapter package
可能重新可做 @suantea 于 31 天前认领，目前没有进行中的 PR。未关闭
- 哪里不对？
needs-triage

难度 2/5 1-3 小时新手友好度 84/100

stacklok/toolhive#6191 · 2026年8月4日创建

维护者通常 1 天内回复
Outgoing strategies differ on no-subject-provider fallback (xaa hard-fails, token_exchange and aws_sts fall back) and it is undocumented
可能重新可做关联的 PR 已关闭且未合并。未关闭
- 哪里不对？
bug

难度 2/5 1-3 小时新手友好度 72/100

stacklok/toolhive#6177 · 2026年8月3日创建

维护者通常 1 天内回复

查看 stacklok/toolhive 的全部 Issue

相似的 Issue

chore(deps): upgrade go.lsp.dev dependencies to v1
未关闭
- 哪里不对？
难度 2/5 1-3 小时新手友好度 68/100

bufbuild/buf#4785 · 2026年11月11日创建

维护者通常 1 天内回复
build: make check-linter version tests deterministic
未关闭
- 哪里不对？
难度 2/5 1-3 小时新手友好度 75/100

dapr/dapr#11102 · 2026年11月11日创建

维护者通常 1 天内回复
GitHub webhook is not subscribed to release events, so `event: release` never triggers
可能已有人在做 @qsun 今天认领。未关闭
- 哪里不对？
难度 2/5 1-3 小时新手友好度 78/100

woodpecker-ci/woodpecker#7542 · 2026年11月11日创建

维护者通常 1 天内回复
[Bug]: secondary restore sends IndexId 0 for every field in AlterLoadConfig (index map keyed by index ID, looked up by field ID)
未关闭
- 哪里不对？
难度 2/5 1-3 小时新手友好度 74/100

zilliztech/milvus-backup#1386 · 2026年11月11日创建

维护者通常 1 天内回复
Pipelined flush no longer observes kill signals after #2042: flush backoffer is built with nil vars
未关闭
- 哪里不对？
难度 2/5 1-3 小时新手友好度 78/100

tikv/client-go#2169 · 2026年11月11日创建

维护者通常 1 天内回复

更多 Go Issue

Reduce log spam of vMCP pod by logging cache sync messages at debug

哪里不对？

评估

调研方向

描述

环境准备

从这里开始

stacklok/toolhive 的其他 Issue

哪里不对？

哪里不对？

哪里不对？

哪里不对？

哪里不对？

相似的 Issue

哪里不对？

哪里不对？

哪里不对？

哪里不对？

哪里不对？

把新 issue 发到你的邮箱