request logs sorting is not reliable #606

New Issue

MrUnknownDE · 2026-04-05T17:26:28+02:00

MrUnknownDE commented

2026-04-05 17:26:28 +02:00

Originally created by @thutex on 11/22/2025

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

OS Type & Version: ubuntu 24.04
Pangolin Version: 1.12.2

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

*Originally created by @thutex on 11/22/2025* ### 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 - OS Type & Version: ubuntu 24.04 - Pangolin Version: 1.12.2 ### 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

MrUnknownDE closed this issue

2026-04-05 17:26:28 +02:00

MrUnknownDE added the bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug labels 2026-04-05 17:26:29 +02:00

Sign in to join this conversation.

Branches Tags

main

dev

dependabot/npm_and_yarn/dev-minor-updates-b4e5d6b9c5

revert-2766-feature/systemd-install-instructions

dependabot/npm_and_yarn/prod-patch-updates-05702d39f2

dependabot/npm_and_yarn/next-16.2.1

dependabot/npm_and_yarn/recharts-3.8.1

alerting-rules

private-site-ha

dependabot/docker/docker/library/node-25-slim

ssh

delete-account

msg-delivery

org-only-idp

cicd

patch

site-targets-auto-login

No Label bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/pangolin#606