feat: include template ID in re-emitted boundary logs (#21618)

Boundary policies are currently defined at the template level, so
including the template ID in re-emitted logs by the control plane
allows policy creators to filter and observe boundary activity for
specific templates. This makes it easier to verify that policies are
working as expected and to debug issues with specific template
configurations.
This commit is contained in:
Zach
2026-01-22 08:37:16 -07:00
committed by GitHub
parent 4c7844ad3d
commit 6d8e6d4830
4 changed files with 8 additions and 0 deletions
+1
View File
@@ -133,6 +133,7 @@ Each boundary audit log entry includes:
| `workspace_id` | The UUID of the workspace where the request originated |
| `workspace_name` | The name of the workspace where the request originated |
| `owner` | The owner of the workspace where the request originated |
| `template_id` | The UUID of the template that the workspace was created from |
| `http_method` | The HTTP method used (GET, POST, PUT, DELETE, etc.) |
| `http_url` | The fully qualified URL that was requested |
| `event_time` | Timestamp when boundary processed the request (RFC3339 format) |