Logs
The Logs section displays a time-ordered record of all requests handled by Obiguard.
Each log entry provides useful data such as the timestamp, request type, LLM used, tokens generated, thinking tokens and cost. For multimodal models, Logs will also show the image sent with vision/image models, as well as the image generated.
By clicking on an entry, a side panel opens up, revealing the entire raw data with the request and response objects.
This detailed log can be invaluable when troubleshooting issues or understanding specific interactions. It provides full transparency into each request and response, enabling you to see exactly what data was sent and received.
Share Logs with Teammates
Every log entry in Obiguard has its own unique URL. Simply copy the link from your browser’s address bar to share it directly with anyone in your organization.
Request Status Guide
The Status column on the Logs page provides an overview of gateway activity for each request.
You can easily monitor and optimize your usage, as Obiguard tracks all gateway features here along with their current states (such as disabled, triggered, etc.).
Debug Requests with Log Replay
Quickly troubleshoot issues by replaying any request directly from the log details page. Click the Replay button to open the request in a new prompt playground, where you can modify and rerun it until you achieve the desired result.
The Replay button will be disabled in the following scenarios:
- The request was sent to an endpoint other than
/chat/completions,/completions, or/embeddings - The virtual key used in the log has been deleted on Obiguard
DO NOT TRACK
The DO NOT TRACK option lets you process requests without storing the request and response data in the logs. When this is enabled, only summary metrics such as tokens used, cost, and latency are recorded; the actual request and response content is excluded.
This is useful for handling sensitive information or meeting data privacy requirements, as it allows you to monitor key operational metrics without logging confidential data.
To activate DO NOT TRACK for a request, set the debug flag to false when creating your Obiguard or OpenAI client, or add the x-obiguard-debug:false header to your request.