feat(audit): search request logs by API key name - #187
Open
stoner-byte wants to merge 1 commit into
Open
Conversation
astaxie
reviewed
Aug 10, 2026
| setRequestPage(1); | ||
| }} | ||
| placeholder={tx("搜索请求 ID、模型、Provider、状态码")} | ||
| placeholder={tx("搜索请求 ID、API Key、模型、Provider、状态码")} |
Owner
There was a problem hiding this comment.
[P2] Please make the searchable API Key fields explicit
“API Key” can reasonably be read as the raw key secret, even though this endpoint intentionally supports only the key name/ID and the test verifies that raw secrets do not match. Because the input is serialized into the URL as q, this wording could encourage an operator to paste a credential into a value that may be retained by HTTP/proxy logs. Could we change this to “API Key 名称或 ID” and make the equivalent English/Japanese translation updates?
Owner
|
@stoner-byte 抓紧修复上面的问题 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Allow the existing request history keyword search to match the name of the API Key that made a request. This makes per-key troubleshooting possible without exposing or searching raw API key secrets.
Related Issue
N/A
Changes
api_keys.namethrough the existingrequest_logs.api_key_idrelation in request-log keyword searches.Type of Change
Verification
go test ./...(backend)go vet ./...(backend)npx tsc --noEmit(frontend)node --test tools/*.test.mjsnode tools/check-doc-translations.mjsnode tools/check-ui-translations.mjsnode tools/check-env-contract.mjsnode tools/check-source-lines.mjsgit diff --checkCompatibility, Security, and Operations
The existing
qquery parameter gains API Key name matching; its request and response shapes are unchanged. No schema migration, configuration, deployment change, or raw API key lookup is introduced.Checklist
.envfiles, databases, backups, or runtime logs are included.start.sh, and deployment documentation where applicable. No environment variables changed.data/model-catalog.yamlremains tracked and catalog changes were reviewed where applicable. No catalog changes.git diff --checkpasses.