-
Notifications
You must be signed in to change notification settings - Fork 34
Add paid-query latency histogram to analytics API #89
Copy link
Copy link
Open
Labels
Stellar WaveIssue proposed for the Drips Stellar Wave programIssue proposed for the Drips Stellar Wave programarea: apiAPI serviceAPI servicearea: dataPersistence and analyticsPersistence and analyticscomplexity: highExpected high implementation complexityExpected high implementation complexitydrips-candidateCandidate for a Drips Stellar WaveCandidate for a Drips Stellar WaveenhancementNew feature or requestNew feature or request
Description
Metadata
Metadata
Assignees
Labels
Stellar WaveIssue proposed for the Drips Stellar Wave programIssue proposed for the Drips Stellar Wave programarea: apiAPI serviceAPI servicearea: dataPersistence and analyticsPersistence and analyticscomplexity: highExpected high implementation complexityExpected high implementation complexitydrips-candidateCandidate for a Drips Stellar WaveCandidate for a Drips Stellar WaveenhancementNew feature or requestNew feature or request
Why this matters
SCF reviewers and investors care whether paid queries are usable in practice, not only whether payment succeeds. A small latency histogram makes provider performance visible without adding a full observability stack.
Scope
Extend analytics output with latency buckets for paid query execution:
<1s;1-3s;3-10s;>10s;unknownwhen latency was not recorded.Suggested files:
apps/api/src/routes/public.tsapps/api/src/lib/persistence.tspackages/shared/src/schemas.tsAcceptance criteria
Wave complexity
High - adds investor-grade performance evidence for paid-query reliability.