Add additional token calculation information to the Limit Azure OpenAI API token usage API Management policy #123618
+1
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…I API token usage API Management policy How does the new APIM policy “Limit Azure OpenAI API token usage” `estimate-prompt-tokens` feature work? How does it estimate the tokens? Only of the prompt or also of the response? What changes, when I activate/deactivate it? The documentation was way too minimal on this. This change adds some additional information about the impact of setting `estimate-prompt-tokens` to false. This is important, because it might cause the probably unexpected behavior of sending requests to the LLM backend, which should have been filtered out by the policy. Please check for correctness by the Product Team.
|
@robinmanuelthiel : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 4c9b755: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add additional token calculation information to the Limit Azure OpenAI API token usage API Management policy
How does the new APIM policy “Limit Azure OpenAI API token usage”
estimate-prompt-tokensfeature work? How does it estimate the tokens? Only of the prompt or also of the response? What changes, when I activate/deactivate it? The documentation was way too minimal on this.This change adds some additional information about the impact of setting
estimate-prompt-tokensto false.This is important, because it might cause the probably unexpected behavior of sending requests to the LLM backend, which should have been filtered out by the policy.
Please check for correctness by the Product Team.