Page MenuHomePhabricator

HTTPS performance & UA adoption metrics
Closed, ResolvedPublic

Description

We're currently flying mostly blind as far HTTPS metrics go; we don't know, for example, what percentage of users supports which versions of TLS or ciphers, or (soon) SPDY/HTTP2. We do have some NavTiming metrics but we don't have a great way of displaying these (dashboards).

We should get more insight there. I've previously experimented with nginx lua + statsd plugin that logged ciphers & protocols and it did work fine but we should think of it more eloquently and deploy it. Probably blocked on T86648.

Event Timeline

faidon raised the priority of this task from to Medium.
faidon updated the task description. (Show Details)
faidon added subscribers: Aklapper, faidon, mark, BBlack.

Thanks for creating this task. It would be even nicer if the description mentioned *all* the research that is needed or ongoing before the big red switch for T49832 is turned. Just titles would suffice. With its current definition the task is too vague, it may range from few hours of work to add some graph for existing data to years of work for entire university departments. :)

For instance, per-country errors %, per-project errors %, per-country navtiming, per-project navtiming, editor retention, editor activation, bounce rate, number or link clicks, ...? (Some unlikely, e.g. bounce rate.)

BBlack claimed this task.

We're not exactly flying blind anymore. Analytics has done a bunch of independent analysis post-switch. We've got cipher/protocol/sessionid metrics going to graphite and tessera, and of course since we're past the switch date we can already see the raw perf impact everywhere else. Considering this done.