Moose RelayKNOW YOUR TRAFFIC
Server usage
Requests, performance, and the calls behind them.
Loading usage…
Request activity
● Successful● Failed
Hover or focus a bar for details.
No requests in this view yet. Usage starts when traffic passes through Moose Relay; earlier requests cannot be reconstructed.
Tool-call payload capture
Off by default. Opting in saves arguments and results for future tool calls. Payloads may contain private content; common credential fields are redacted, but arbitrary text cannot be reliably scrubbed. Encrypted at rest, limited to 32 KB per argument/result preview, retained for 30 days.
By server
Select a server to inspect its traffic| Server | Requests | Errors | Avg. gateway time |
|---|
Request log
| Time | Server / operation | Tool | Outcome | Gateway time | Details |
|---|
One entry per routed operation. Gateway time runs from request arrival in Moose Relay until the response is sent, including authentication, queueing, locks, logging, and all upstream work. Fan-out entries share the same gateway request ID and total time; do not add those totals together. Client-side waiting and network time outside Moose Relay are not included. Older entries without full gateway timing and connection tests show no duration and are excluded from timing statistics. Account-limit rejections are logged separately as Moose Relay gateway / Rate limited, without payloads, and appear in the all-servers chart and log. Select a specific server to view only operations routed to it. Protocol handshakes and internal pagination are not counted separately. Charts use UTC buckets; log times use your local timezone. Logs expire after 30 days. Server logs are deleted with their server; all logs are deleted with their account.