Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-architecture-council] Download stats reliability and SLA

On 2020-03-17 3:52 p.m., Gunnar Wagenknecht wrote:

On Mar 17, 2020, at 20:11, Denis Roy <denis.roy@xxxxxxxxxxxxxxxxxxxxxx> wrote:

The problem is injection points -- we rely on the Find a Mirror script, and p2.statsURI for injecting a stats entry. If a project links to a mirror directly, or download.eclipse.org directly, or worse -- if a user follows a direct link, then no stats are generated for those downloads.


Wasn't there a point in time when web server access logs were used for download stats?


We pull the /stats (p2.statsURI) entries from the logs already. We could pull in download.eclipse.org logs directly, but my fear is that folks would bypass the Find a Mirror thing and just link to download.e.o directly (using mirrors is the carrot for stats).

Also, the DB already has 1bn rows of download records for the last 365 days.


Denis



-Gunnar

_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
--

Denis Roy

Director, IT Services | Eclipse Foundation, Inc.

Eclipse Foundation: The Platform for Open Innovation and Collaboration

Twitter: @droy_eclipse


Back to the top