On Mon, May 16, 2016 at 12:40 PM, Greg Sutcliffe <[email protected]> wrote:
> On 13 May 2016 at 10:56, Ohad Levy <[email protected]> wrote: > > > > What about repository metadata queries? (That should be anyone with yum > repository configured doing a yum update/search etc). > > Can't say from the apache logs - you only get something like: > > <ip redacted> - - [15/May/2016:06:34:41 +0000] "GET > /releases/1.9/el6/source/repodata/repomd.xml HTTP/1.1" 200 2991 "-" > "urlgrabber/3.9.1 yum/3.2.29" > > So we can see the user-agent and the uri_path, but just because someone > did a query on the el6 repodata, doesn't mean they're actually using it. > > At the moment I don't index this data, just filtering to *.(rpm|deb) on > the uri_path results in 120Mb of logs to parse. Including *.xml makes it > too large. > > > It would also be interesting to know how many el6 users are on > unsupported Foreman (e.g. 1.9 and below). > > All the yum logs will show are people who upgraded to, or installed, an > unsupported version during the time window. There are downloads logged for > this time period for versions all the way back to 1.0, but I would regard > anything other than the supported version as highly unreliable and probably > far more to do with mirroring than actual installs. > > Without phone-home data from existing instances, you've got nothing about > current installs that haven't be upgraded. I don't think you can ever give > much trust to download data - we did talk about phone-home stats a while > ago, perhaps you should write it up as an RFC :) > > Since you ask though, this is the el6 data I can pull from my logs db. > Note that my parsing of uri_path for things like foreman-release* and > rhscl* is far from perfect yet... > > > downloads=# select > > name, substring(version from '\d\.\d*') as v, > > os,count(name) as total from log_lines > > where name LIKE 'foreman' and os='el6' > > and logdate >= (now() - interval '1 month') > > group by name,os,v order by v desc; > > > > > name | v | os | total > > ---------+------+-----+------- > > foreman | 1.12 | el6 | 206 > > foreman | 1.11 | el6 | 1872 > > foreman | 1.10 | el6 | 334 > > foreman | 1.9 | el6 | 115 > > foreman | 1.8 | el6 | 98 > > foreman | 1.7 | el6 | 59 > > foreman | 1.6 | el6 | 44 > > foreman | 1.5 | el6 | 707 > > foreman | 1.4 | el6 | 227 > > foreman | 1.3 | el6 | 19 > > foreman | 1.2 | el6 | 18 > > foreman | 1.1 | el6 | 25 > > foreman | 1.0 | el6 | 5 > > (13 rows) > > Note the 707 downloads of 1.5 in the last month - this is why I don't > trust this data as a source of what people are *using* ;) > TBH: I believe those numbers are a reflection of real state, I've seen a lot of old foreman running around, which make some sense (assuming its a critical piece of the infrastructure). IMHO if you see a yum user agent grabbing a metadata file thats a consistent and reliable way to know that there is a configured system using it, it might be a stale repo setting from an old install, but imho a valid metric. Ohad > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
