Enhancement: Expose Response Headers and Rate Limit Metrics, Efficiency Logging #120
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.
This pull request introduces an array of updates aimed at providing greater visibility for response-level information and optimizing processing efficiency. Key enhancement details include the following:
Additions:
setResponseHeaders
andgetResponseHeaders
methods have been implemented to allow the storage of response headers.setRateLimitInfo
,getRateLimitInfo
, andhydrateRateLimitInfo
methods have been implemented to provide visibility of rate-limiting information.setProcessingMs
,getProcessingMs
, andhydrateProcessingMs
methods have been implemented to monitor processing time in milliseconds.setHeaderFunction
method has been implemented to manage header formatting and assignment.Refactoring:
These changes will assist in monitoring usage, complying with rate-limits, and optimizing processing speed. Further testing and feedback are appreciated.
Commit log: