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
How to fix: Lago events ingested but events_count stays 0 in current usage API. The verified fix from the maintainer thread, distilled into reusable steps.