-
Notifications
You must be signed in to change notification settings - Fork 1.4k
feat(trace): Trigger API Key refresh on 403 #45674
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
gh-worker-dd-mergequeue-cf854d
merged 8 commits into
main
from
ichinaski/api-key-refresh-retry-payloads
Feb 23, 2026
Merged
Changes from 1 commit
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
4a0a24e
feat(trace): Trigger API Key refresh on 403
ichinaski 646b8a9
Refactor API Key Management
ichinaski e622bc0
Merge branch 'main' into ichinaski/api-key-refresh-retry-payloads
ichinaski 21e08e6
add release notes
ichinaski 185655e
check return values
ichinaski 09289f4
Merge branch 'main' into ichinaski/api-key-refresh-retry-payloads
ichinaski d774a1d
Add throttling on Trace Agent side
ichinaski c9a1cef
replace fmt with errors.New
ichinaski File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One concern I have here is what do we do when the Forbidden status code is legit / the API key has been rotated and the customer is not using RC / api key refresh? I suppose it's probably not a big deal since if the API key is bad then we're going to drop things anyways, but it does mean we'll retry requests more than we probably should? I'm wondering if there's a way we can gate these retries so that they only retry when we know we can try to get a new api key (And then only retry after we have a new api key?).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a good question. I initially approached the issue from that angle, but quickly saw that keeping track of invalid keys and blocking the sender had it's own tradeoffs: more complex api key changes propagation, refactor goroutines to avoid race conditions when reading/writing the key... and the sender will still be unable to send other payloads if the api key is invalid. This concern you raise is also the reason I'm not 100% fond of the proposed solution 🤔