1186080 - Consider using a hash of clientId to key Unified Telemetry data (instead of using clientId directly).

Status: RESOLVED WONTFIX

(Cloud Services Graveyard :: Metrics: Pipeline, defect, P2)

Description

[Mark Reid [:mreid]]

In the interests of placing an upper bound on the length of the primary key used for longitudinal analysis, it may be better to use a hash of the raw clientId instead of the clientId itself. 

I filed this bug because I noticed a few crash submissions with the following:
"clientId":"593836                                                                             8c-ddc6-4cfa-91b2-24614767c823"

With all kinds of extra spaces.

Is the tradeoff in complexity and indirection worthwhile?

Comment 1

[Mark Reid [:mreid]]

As discussed in today's triage, it would be better to validate that the client is sending well-formed UUIDs for the "clientId" field and then non-UUID values to the error stream on the server.

Comment 2

[Thomas Huelbert]

Based on the discussion, should we close this as invalid?

Comment 3

[Mark Reid [:mreid]]

Yep.