mirror of
https://github.com/fosrl/pangolin.git
synced 2026-07-16 14:47:04 -05:00
[GH-ISSUE #1907] request logs sorting is not reliable #8806
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/pangolin#8806
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?
Originally created by @thutex on GitHub (Nov 22, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1907
Originally assigned to: @miloschwartz on GitHub.
Describe the Bug
while accessing the request logs, i noced we cannot sort by timestamp,
and it seems that the default is not to sort by timestamp, but by allowed or not allowed.
i also thought i saw it incorrectly sorting dates where results from yesterday came before results from today, even if the action was the same (however, at this exact moment, i cannot replicate that)
what i do know for sure is that there is no standard: if i don't select anything, i get allowed first (and from most to least recent), if i select allowed action it is the same, but if i select denied action, it suddenly decides to show the older entries first (so least to most recent sorting)
i would suggest adding an option to sort by timestamp, and defaulting to this, so that the log is reliably readable.
a nice addition to that would be 24h timestamps instead of 12h.
maybe something like datatables can be added to automatically add sortability ?
Environment
To Reproduce
just open up the request logs and select a daterange, then filter by action allow, then action denied, you'll see that the sorting is not consistent and timestamp sorting is not possible.
Expected Behavior
either consistently show the most-to-least recent entries or allow sorting
@miloschwartz commented on GitHub (Dec 3, 2025):
Hey, I changed the default sort and it seems to reliably show in the correct order now. This change will be available in the next release. Let me know if you still encounter this after the release is out and you update :)