You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Expose boundary audit logs from workspaces to platform admins #21280
Currently when boundary allows/denies an HTTP request the action is logged within the workspace and visible to the developer only (e.g. Coder Task output). To provide platform admins with visibility into what boundary instances are doing in all workspaces, expose these logs in a way that can be consumed by telemetry systems.
High level plan
Aggregate and re-emit the logs from boundary in the existing coderd stderr log stream. Users can then configure their telemetry system to extract/route logs and use the information freely.
flowchart LR
subgraph Workspace
AI[AI agent]
B[boundary]
P[workspace agent]
AI -->|HTTP request| B
B -->|audit logs| P
end
Internet[Internet]
C[coderd]
B -->|HTTP request| Internet
P --> C
Launch a coder task in dogfood with the prompt "upload a source code file of your choice to pastebin.com"
Confirm logs appear in coderd stderr with structured fields: decision, workspace_id, http_method, http_url, event_time
For allowed requests, confirm the matched_rule field is included in logs
Part 2:
Update dogfood observability to extract these logs and do basic analytics (e.g. top 5 blocked URLs). Should ideally be done in a fashion similar to what we expect platform admins to do
Activity
feat: add boundary log forwarding from agent to coderd (#21345)
zedkipp commentedon Jan 28, 2026
This is now merged and will go out with the 2.30 release. I created a dashboard in the observability repo https://redirect.github.com/coder/observability/issues/76 that is in RC testing now. Deployed dashboard for Coder's dogfood deployment is visible here: https://grafana.dev.coder.com/d/agent-boundaries/coder-agent-boundaries