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
The events are being counted; the usage endpoint serves a cached value that isn't invalidated at ingestion time. The fix that worked for reporters: clear the Redis cache, or simply call the current_usage endpoint again — it refreshes its ca