fedora 40 and above missing on images on data-analysis.fedoraproject.org/csv-reports/images #12426
Labels
No labels
announcement
anubis
authentication
aws
backlog
blocked
bodhi
ci
cloud
communishift
copr
database
day-to-day
dc-move
deprecated
dev
discourse
dns
downloads
easyfix
epel
firmitas
forgejo_migration
Gain
High
Gain
Low
Gain
Medium
gitlab
greenwave
hardware
help wanted
high-trouble
koji
koschei
lists
low-trouble
medium-trouble
mirrorlists
monitoring
Needs investigation
odcs
OpenShift
ops
outage
packager_workflow_blocker
pagure
permissions
Priority
Needs Review
Priority
Next Meeting
Priority
🔥 URGENT 🔥
Priority
Waiting on Assignee
Priority
Waiting on External
Priority
Waiting on Reporter
rabbitmq
release-monitoring
releng
request-for-resources
s390x
security
SMTP
sprint-0
sprint-1
src.fp.o
staging
unfreeze
waiverdb
websites-general
wiki
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
No milestone
No project
No assignees
8 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
infra/tickets#12426
Loading…
Add table
Add a link
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?
could fedora 40, 41 and 42 be included in the graphs available at https://data-analysis.fedoraproject.org/csv-reports/images/summary.html
Metadata Update from @phsmoura:
cc: @james
I know about the numbers behind this, but not what generates the graphs etc.
cc @mattdm ?
This is done via a set of scripts not attached to the work James has been doing. The older data graphs were were to be end-of-lifed around Fedora 40 and replaced with ones generated weekly from the dnf countme data.
The scripts are a python and awk which do a rough count of 1 entry per arch, release,ip/day and then writes out a csv file. That csv file is then run against some rough gnuplot graphs which get updated daily.
All of these were really a short term hack which turned into a permanent solution so updating to newer releases requires a lot of manual hacking of scripts, gnuplot graphs and the existing CSV files to deal with the newer data. At the moment the only data I would consider it useful for is the EPEL-6,8,9 numbers and historical data for other items.
A better solution would be to finish the 'make a graph every week from the countme data' project and keep an older set of pictures with an end-date of when they were last valid (Jun 2024?).
The hacky stuff appears to be under roles/web-data-analysis/files/
Perhaps it's not hard to just add 40+ for now?
Or perhaps someone can finish the new thing... but I don't even know the status of that? was someone working on it?
I thought that the new thing is already finished and running.
Last year, I was playing with a rewrite of https://pagure.io/brontosaurusifier which includes a frontend for the graphs. I didn't finish it then, but (obviously) I kep the code and it probably wouldn't be hard to wrap it up. I could make PR for stg or communishift, if people want me to push on with it.
It would be nice to have for sure...
9 months later.... anyone willing to look into what it would take to finish off the new one or just trivially add 40+ to the hacky one?
So ... I spoke to Matthew today, and have had a look at a bunch of the code.
Roughly what happens now:
...trying to run
velociraptorizeris ... not fun. However even then you can't just add F40-F44 because the data from mirrorsdata-all.csv also only goes up to F39 ... so we'd need to altermirrors-data.awkto generate the new columns and velociraptorizer to use them, and I wouldn't be shocked if smooge is the only one who knows awk that well ;).Matthew said he hoped he'd have free time on friday to look using the countme data directly, and/or maybe something else to generate graphs. If that doesn't close this issue then we def. need to give it more than low-trouble.
Oh, actually -- the images on the server are generated by Smooge's script, not velociraptorizer.
On that note, I hacked a python script up to get the weekly unique IP data out of totals.db for specified repo-tags and put them into a single CSV file ... then did what all the cool kids were doing before AI and found a graph as a service thing:
Comparing F40+ (2024-) unique IP hits.
https://datawrapper.dwcdn.net/BzYk3/2/
Comparing F32+ (2020-) unique IP hits.
https://datawrapper.dwcdn.net/cA5zb/1/
EPEL 5+ (2012-) unique IP hits. (for the big numbers)
https://datawrapper.dwcdn.net/iuRY0/1/
I just got these in my email box.. do you still need info from me on my messed up really bad program?
The images on the website are all done via a 'POC goes directly into production' method of using gnu plot I wanted to get the velociraptor tooling instead as the graphs were much nicer. I would suggest not using a graph as a service thing because they tend to become 'crap this is costing me money.. better just fill anyone using its browser with porn spam' at some point.
Yeh, we've all been there to some degree. Although I looked at the git log and it's been in prod. for 10 years now, achievement unlocked ;)
Hopefully we can replace it with another POC before this one hits 11.
Was def. not planning on using it more than a couple of times, but wanted something as easy as possible to let people see data for the last couple of releases (I do realize how this sounds next to your 10 yr POC).
I think we are good. We need to come up with a plan and repoint this issue.
I am working on moving Brontosaurusifier to Graphana, and as part of that also adding the long-format unique-ip data that James worked on, like two years ago now. That has the big advantage of not ever needing column additions; new things just automatically get picked up.
If there is Hot Demand for velociraptorizer-style static images too, I can keep that for selected data.
But in any case, I thnink the old tooling can be retired.