This seems extremely reasonable. Doing some kind of measurement of the use of Web sites is pretty much standard industry practice and critical if you are going to know how the site is being used and whether it works.
I would second Mark Nottingham's call to do performance monitoring and include datatracker. Anecdotally, we see real performance problems here and measuring that is the first step. I'd also suggest that some sort of uptime monitoring (pingdom, etc.) would be a good idea, though perhaps it's a different project.
-Ekr
On Tue, May 21, 2019 at 8:18 AM Roman Danyliw <rdd@xxxxxxxx> wrote:
Hi!
The Internet Engineering Steering Group (IESG) is seeking community input on implementing web analytics on www.ietf.org ("the website").
There is currently no accurate data reported about visits to the website. For example, it is not possible to understand: which pages are most commonly visited; which paths visitors travel to find IETF meeting registration pages; or whether introductory information, such as tutorials, leads to further exploration of website content. Web analytics would provide insight into overall utilization and inform future improvements to the website.
In consultation with the tools team, Greg Wood developed an implementation plan to integrate a self-hosted analytics package into the existing infrastructure. The full details of this proposal are available at:
https://www.ietf.org/iesg/docs/www.ietf.org-AnalyticsProposal-forReview.pdf
The IESG appreciates any input from the community on this proposal and will consider all input received by June 4, 2019.
Regards,
Roman
(as the IESG Tools Liaison)
