feat: add a requests / consumers chart based on referer#11
Draft
BatLeDev wants to merge 6 commits into
Draft
Conversation
Processing traffic is becoming internal (routed through the private data-fair url) and will no longer reach nginx, so the processing dimension is removed: - daemon no longer reads the x-processing slot (no Processing user-class suffix, no processing object stored) - api drops the "processing" split and the processingId filter - ui drops the "requests by processing" chart and the processing labels The daily-api-metric schema keeps the processing $def and the userClass enum, and the mongo unique index keeps processing._id, so previously collected documents stay valid and readable. The nginx log slot is left in place (the daemon just ignores it) until the coordinated log_format change that will repurpose it for the future x-service header.
BatLeDev
changed the title
…Category "other" Requests recorded before refererCategory was introduced have no such field; treat them as 'other' both in the split aggregation and in the filter, instead of surfacing them as a separate unlabeled bucket.
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
1 participant
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.
Replace the removed "processings" chart with a "Requêtes / consommateurs" chart, classifying traffic purely from the already-logged referer (no ingress/log_format change — nginx log slot 10 stays unused).
refererCategory(backoffice/embed/app/mcp/other) from the referer's host (compared to the request's own host) and path, stored likerefererDomaindaily-api-metric/agg-query/agg-resultschemas gain therefererCategoryfield/filter/split option; the generic agg split handles it with no extra service codeWhy: processing traffic is becoming internal and no longer reaches nginx, so the freed slot isn't reused — this ships a simpler, ingress-free classification instead.
Heads-up: a companion change in
data-fair/mcptags our own hosted MCP server's outgoing calls with a/mcpreferer so that traffic lands in themcpbucket; third-party/self-hosted MCP bridges fall back toother, as expected. AddingrefererCategoryto the mongo unique index is safe against historic documents (a widened key can't collide). Historic documents withoutrefererCategoryrender as "Aucune" in the UI.