Page MenuHomePhabricator

Safe-guard against double counting SSL zero traffic
Closed, DeclinedPublic

Description

Kraken's pageview definitions never properly addressed the fact that
we log SSL requests twice (Once for the request at the SSL terminator,
and once for the request from the SSL terminator to the caches).

Up to recently, this peculiarity was not an issue for Zero, as we
were not having SSL traffic in zero. That however changed now.

Currently, Kraken is still doing the correct thing (throwing away the
log line from the SSL terminator, and counting only the request from
the SSL terminator to the caches), but only due to the fact that SSL
terminators do not set a MIME type—which is more than just brittle.

So kraken is doing the correct thing more as a side-effect than by
proper design. This issue becomes more and more relevant, as we're
seeing more and more SSL traffic.

We should teach kraken to properly detect requests from SSL
terminators and consequently filter them.


Version: unspecified
Severity: normal

Details

Reference
bz62980

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 2:55 AM
bzimport set Reference to bz62980.
bzimport added a subscriber: Unknown Object (MLST).

bingle-admin wrote:

Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/analytics/cards/cards/1492