Logs
Use logs and events to explain what the relay actually did.
Not every visibility stream serves the same purpose. Binboi benefits from keeping raw relay logs, activity events, and richer request-level views conceptually separate so developers can start with the right lens.
Types
Raw logs versus request views
A healthy docs system teaches users which visibility surface to consult first.
Visibility layers
| Layer | Best for | Examples |
|---|---|---|
| Raw relay logs | Transport truth | Token rejected, agent connected, proxy error, stream closed. |
| Activity events | Operator history | Tunnel reserved, token created, domain verified, session revoked. |
| Request views | One-request debugging | Headers, payload preview, response status, duration, target service. |
Current MVP reality
History
Activity events
Activity events are the operator-facing history of what changed in the control plane.
Use activity events to answer questions like who created a token, when a tunnel was reserved, or whether a domain verification step completed.
These events should be quieter and more human-readable than transport logs because their audience is often the operator, not only the debugger.
Lifecycle
Tunnel lifecycle events
A tunnel has a lifecycle, and the logs should reflect it clearly.
Typical lifecycle progression
text
Tunnel reserved
Agent authenticated
Tunnel connected
Request forwarded
Proxy error or upstream response
Tunnel disconnected
Token revoked or rotatedPractice
How to use logs well
Good operators use the right level of detail for the question they are trying to answer.
Start with activity events when you suspect a configuration or lifecycle issue.
Move to raw relay logs when you need transport truth, such as authentication failure or proxy behavior.
Use request views when the tunnel is healthy but the application-level outcome is confusing.