Requests can be tagged: metadata, x-llmgw-tags and the user field on the usage record, and counted by the tags router.tag_labels names
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
1 parent
e59ff52932
commit
29a7347df2
19 files changed
+436
-17
No files matched your search
+6
-1
@@ -412,7 +412,12 @@ portal is not done — the page shows; the console and ctl change.
|
||||
templates driven by `server init` or the console; llmgw-native webhooks
|
||||
for model parked, budget spent, update available (from the reconciler
|
||||
and `modelserve`).
|
||||
6. **Request metadata and tags (S).** Accept `metadata`/`user` from the
|
||||
6. **Done (branch `features-c2`):** `metadata`, `x-llmgw-tags` and `user`
|
||||
on the usage record (migration 0023), `ctl request` shows them,
|
||||
`router.tag_labels` metrics with 100 values per tag. Left: export and
|
||||
`ctl usage` by tag or end user (the hourly and daily sums do not carry
|
||||
tags; it would read the request records, within their retention).
|
||||
**Request metadata and tags (S).** Accept `metadata`/`user` from the
|
||||
body or `x-llmgw-tags`; store on the usage row; tenant metric labels
|
||||
behind an allowlist. `router/handlers.go` parse, `accounting/recorder.go`.
|
||||
7. **Canary and weighted A/B between model revisions (M).**
|
||||
|
||||
Reference in new issue
Block a user