mirror of
https://github.com/fosrl/pangolin.git
synced 2026-07-16 06:08:33 -05:00
[GH-ISSUE #2113] Analytics page doesn't respect default filters #6867
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 @depado on GitHub (Dec 18, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2113
Describe the Bug
The analytics page doesn't display the proper data and does not respect the default filters.
Default filters
When opening the page with no filters:
There seem to be an issue in the API response of
/api/v1/org/<myorg>/logs/analyticsas it does not return the most recent data:API Response
As today is the 18th, we are missing three days.
Changing the end date
Changing the end date or any date changes the API call options and properly returns all available data:
Environment
To Reproduce
Have more than 5 days of request logs history and head to the Analytics page.
Expected Behavior
The analytics page should respect the default time range displayed
@mighty-services commented on GitHub (Feb 5, 2026):
Hy There,
first of all: THANK YOU SO MUCH FOR ALL YOUR WORK! I'm amazed by all the features you added recently.
I have Pangolin running for quite some time. During this time, you added the Analytics feature. When I open it on my machine, the countries-list is empty. I see the graph mentioned above, but thats it:
I searched through your docs and find the part, where you can enable telemetry: https://docs.pangolin.net/self-host/telemetry
I did this, restarted my stack and it's still empty, even after some hours of letting it populate.
I installed another pangolin stack for my friend just recently and there, the countries-list is populated.
Both instances running on 1.15.1 community edition. The only difference I see so far is:
What am I missing here?
@mighty-services commented on GitHub (Feb 5, 2026):
AH! I found out, that I had to add the GeoLite2 Features described here: