Logs Export
Easily access your Portkey logs data for further analysis and reporting
Logs export feature is only available for Production and Enterprise users.
At Portkey, we understand the importance of data analysis and reporting for businesses and teams. That’s why we provide a comprehensive logs export feature for our paid users. With this feature, you can easily request and obtain your Portkey logs data in a structured JSON format, allowing you to gain valuable insights into your LLM usage, performance, costs, and more.
Requesting Logs Export
To submit a data export request, simply follow these steps:
- Ensure you are an admin of your organization on Portkey.
- Send an email to [email protected] with the subject line
Logs Export - [Your_Organization_Name]. - In the email body,
- Specify the time frame for which you require the logs data. Pro plan supports logs export of last 30 days.
- Share names of the specific columns you require (see the “Exported Data” section below for a complete list of available columns).
- Our team will process your request and provide you with the exported logs data in JSON format.
Note: Portkey only supports data exports in the JSONL format, and can not process exports in any other formats at the moment.
Exported Data
The exported logs data will include the following columns:
| Column Name | Column Description / Property |
|---|---|
| created_at | Timestamp of the request |
| request.body | Request JSON payload (as seen in the Portkey logs) |
| response.body | Response JSON payload (as seen in the Portkey logs) |
| is_success | Request success status (1 = success, 0 = failure) |
| ai_org | AI provider name |
| ai_model | AI model name |
| req_units | Number of tokens in the request |
| res_units | Number of tokens in the response |
| total_units | Total number of tokens (request + response) |
| cost | Cost of the request in cents (USD) |
| cost_currency | Currency of the cost (USD) |
| request_url | Final provider API URL |
| request_method | HTTP request method |
| response_status_code | HTTP response status code |
| response_time | Response time in milliseconds |
| cache_status | Cache status (SEMANTIC HIT, HIT, MISS, DISABLED) |
| cache_type | Cache type (SIMPLE, SEMANTIC) |
| stream_mode | Stream mode status (TRUE, FALSE) |
| retry_success_count | Number of retries after which request was successful |
| trace_id | Trace ID for the request |
| mode | Config top level strategy (SINGLE, FALLBACK, LOADBALANCE) |
| virtual_key | Virtual key used for the request |
| runtime | Runtime environment |
| runtime_version | Runtime environment version |
| sdk_version | Portkey SDK version |
| config | Config ID used for the request |
| prompt_slug | Prompt ID used for the request |
| prompt_version_id | Version number of the prompt template slug |
| metadata.key | Custom metadata key |
| metadata.value | Custom metadata value |
With this comprehensive data, you can analyze your API usage patterns, monitor performance, optimize costs, and make data-driven decisions for your business or team.
Support
If you have any questions or need assistance with the logs export feature, reach out to the Portkey team at [email protected] or hop on to our Discord server.
Was this page helpful?