On Tue, 6 Nov 2018 at 03:42, Anatoli Babenia <anatoli@xxxxxxxxxxxxx> wrote: > I am just going to concentrate on one part of this email to try and cover things once. > > Currently there is no way to know what > > packages are being installed/downloaded the most. yum and dnf > > downloads not provide those answers on purpose (it would require more > > computational power on the servers than we have and it can't be easily > > made anonymous. The data we can get is only basic information like > > 'what version of yum/dnf used', 'what arch was asked for', 'what was > > the version of Fedora/EPEL wanted' and 'what was the public ip > > address'. This loses all kinds of additional information and masks > > things like proxies, mock builds, etc which inflate/deflate numbers in > > different ways. > > Just a hypothesis. If HTTPS/SSH and dnf protocol uses fixed size packets > and encryption increases the size proportionally, then I can guess the > combination of packages being installed based on time of request and > request size, so it doesn't help to hide that. > That isn't downloaded from Fedora but from any of a thousand mirrors so there is no way for us to see what was downloaded or installed. All that is logged is data like the following: 209.132.184.33 - - [01/Nov/2018:04:02:57 +0000] "GET /metalink?repo=fedora-27&arch=x86_64 HTTP/1.1" 200 18196 "-" "dnf/2.7.5" 209.132.184.33 - - [01/Nov/2018:04:02:58 +0000] "GET /metalink?repo=fedora-27&arch=x86_64 HTTP/1.1" 200 18196 "-" "dnf/2.7.5" 209.132.184.33 - - [01/Nov/2018:04:03:11 +0000] "GET /mirrorlist?repo=epel-7&arch=x86_64 HTTP/1.1" 200 2428 "-" "urlgrabber/3.10.1 yum/3.4.3" All the size data is the metalink mirrorlist xml file which will tell your client which mirrors to go to. yum/dnf then goes to a mirror and pulls out what files it wants from that repository. The data on that is harder to get because yum/dnf do not say 'this person wanted to install 'qdigidoc' It instead gets the repository data, calculates the dependencies and requirements and starts pulling down all the files needed so that qdigidoc can be successfully installed. In the case of 'leaf' packages it might be easier to figure out but if something requires qdigidoc or something similar it then gets lost in the shuffle. The reason you did not see any mirrors in nagios, is that the vast majority of them are run by volunteers who are also doing the same for Debian, Mandrake, SUSE, etc. They do not share their data with us and it would be hard because they also have other sites intermixed. We do not monitor them in our nagios system because we do not run them and do not have any way to fix their problems. -- Stephen J Smoogen. _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
