service · inferred from evidence
current_usage endpoint
An endpoint in Lago that serves cached usage data and invalidates its cache upon being called.
- Lago events ingested but events_count stays 0 in current usage API
Events POSTed to /api/v1/events were accepted (returned a lago_id) and visible in the developer events UI, but the current usage API kept returning events_count = 0 for a count_agg billable metric (code chat_number). Another user hit the sa