[Bug]: Connector Activity docs promise Denied outcomes that are never recorded
维护者通常 1 天内回复
评估
- 难度
- 1/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 88/100
- Issue 类型
- 文档
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- javascript
调研方向
阅读 docs/connector-gateway/connectors.mdx 中的“Review activity”部分，以及 docs/connector-gateway/support-connector-access.mdx 中的第 3 步。更新这两处，说明 Activity 目前只显示允许的调用，缺少调用可能是客户端问题，也可能是策略拒绝；指引管理员查看 Connector Gateway audit log，以区分这两种情况。完成标准是两处都不再承诺会记录 Denied 结果，并提供一致的故障排查指导。
由索引模型根据 Issue 内容生成。
描述
Page or section
docs/connector-gateway/connectors.mdx, "Review activity"docs/connector-gateway/support-connector-access.mdx, "Check a user's access", step 3
What's wrong?
Both pages say a connector's Activity tab lists each call's Outcome as Allowed or Denied. The troubleshooting step then reads: "A denied call points to the policy; no call at all points to the client configuration or connection."
Denied calls are never recorded in Activity. The usage emitter doesn't attribute a denied call to its connector, so the per-connector read can't return it (stacklok/stacklok-enterprise-platform#3901). On the demo cluster, blocking a tool for a group and calling it twice produced failed calls in the client and nothing in Activity. The audit log records the same refusals as application_error, not denied (stacklok/stacklok-enterprise-platform#5758).
So today, an admin following step 3 for a user blocked by policy sees no call at all. The docs then tell them to look at the client configuration, which is the wrong conclusion.
Suggested fix
Until the platform issues are fixed:
- In "Review activity", say that the tab currently shows allowed calls only, and that refusals by connector policy or a group tool restriction don't appear there.
- In "Check a user's access", rewrite step 3 so that "no calls" covers both client problems and policy refusals, and point admins to the Connector Gateway audit log to tell them apart.
When #3901 and #5758 land, restore the Denied wording and say which audit outcome a policy refusal produces.
Additional context
Found while walking through demo flows on the demo cluster, October 27, 2026.
Fully or partially written by an AI agent.
- 主要语言
- JavaScript
- 星标
- 4
- 派生
- 4
- 平均合并
- 17 小时 57 分钟
- 30 天内合并 PR
- 87
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
stacklok/docs-website 的其他 Issue
-
documentation enhancement needs-triage
难度 2/5 1-3 小时 新手友好度 84/100
stacklok/docs-website#1285 ·
维护者通常 1 天内回复
-
documentation enhancement needs-triage
难度 2/5 1-3 小时 新手友好度 82/100
stacklok/docs-website#1258 ·
维护者通常 1 天内回复
-
documentation enhancement needs-triage
难度 1/5 1 小时以内 新手友好度 85/100
stacklok/docs-website#1241 ·
维护者通常 1 天内回复
-
bug documentation needs-triage
难度 2/5 1-3 小时 新手友好度 72/100
stacklok/docs-website#1149 · 2 条评论 ·
维护者通常 1 天内回复
-
needs-triage
难度 2/5 1-3 小时 新手友好度 68/100
stacklok/docs-website#1143 ·
维护者通常 1 天内回复
查看 stacklok/docs-website 的全部 Issue
相似的 Issue
-
[guide] AGENTS.md claims the coverage gate, e2e and full lint run on every PR after ADR 0011 focused validation可能已有人在做 @hivecommons-hive 今天认领。 未关闭agent/guide documentation hive/claimed-by-guide stage/040-covered-by-pr
难度 2/5 1-3 小时 新手友好度 81/100
维护者通常 1 天内回复
-
check:passed feeds:add
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 4 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
all-contributors/cli#587 ·
维护者通常 1 天内回复
-
RGAA5
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 8 天内回复
-
feedback simulation workshop
难度 2/5 1-3 小时 新手友好度 65/100
githubnext/gh-aw-workshop#5157 ·
维护者通常 1 天内回复