Enhancement: Expose Response Headers and Rate Limit Metrics, Efficiency Logging #121
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This pull request introduces several enhancements to the
open-ai
project. Key changes include exposing response headers, rate limit metrics, and improvements in efficiency logging.Key Changes
processingMs
), providing insights into the performance and efficiency of API requests.Files Changed
src/OpenAi.php
: Major changes include:$responseHeaders
and$rateLimitInfo
.hydrateRateLimitInfo
andhydrateProcessingMs
methods for processing the corresponding metrics.Impact
These enhancements will provide users with more control and transparency when interacting with the API. The exposure of rate limits and processing times will aid in efficient API usage and troubleshooting.
Usage
getRateLimitInfo(): returns an array of key-value pairs containing all of the ratelimit info provided via the OpenAI Api response headers:
$rateLimitInfo = $OpenAi->getRateLimitInfo();
getProcessingMs(): returns an int equal to the server request/response processing time provided via the OpenAI Api response headers:
$processingMs = $OpenAi->getProcessingMs()
From the OpenAi Docs: