A slow item list's trace does not say which list it was #287
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The prod check of 2026-10-19 found 11 /api/entries requests of 0.5-0.8 s overnight (02:00-08:00 UTC, host load under 9) among others of 80-100 ms, the time all in the entries_in step (trace bab1f4e8f2c1b6da9930ce70fb434fdc). The trace has the path but not the query: which filter, sort, page or whether a search, so there is no telling which list was slow or why. Query:
{resource.deployment.environment.name="production" && resource.service.name="ipx" && name="step" && duration > 500ms} | select(span.of).Fixed in
6daab69: the entries_in step now carries filter, sort, dir, offset, limit and whether a search (not its words). Deployed as 0.x -dev on 2026-10-19 14:07 UTC; seen in production traces, e.g. {"filter":"unread","sort":"published",...}. Find a slow list with{name="step" && span.of="entries_in" && duration > 500ms} | select(span.filter, span.sort, span.offset).