Basic analytics for websites #89
Labels
No labels
cat
bug
cat
feature
cat
idea
cat
performance
cat
reliability
cat
security
cat
ui
difficulty
high
difficulty
low
difficulty
mid
prio
high
prio
low
prio
mid
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/guichet#89
Loading…
Add table
Reference in a new issue
No description provided.
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?
It needs some clearing about what excatly would be good to have, but I was thinking that some server-side basics analytics for websites visits would be something nice to get some metrics without having to install some external and more complex statistics solutions.
My inspiration is obviously Netlify's analytics (limited to 30 days) https://docs.netlify.com/monitor-sites/site-analytics/
Some data I'm thinking would be nice to have:
Maximilien mentioned https://quickwit.io as a stats solution to look at
Quickwit is a log storage and query backend, so it can be abused (with tricot HTTP logs) to get statistics on website request from a backend PoV, but it's definitely not in itself a tracking tool in the spirit of google analytics and plausible. For example I'm not sure we could get "unique visitors" that way.