Closed Bug 1174358 Opened 9 years ago Closed 9 years ago

Add the session related fields from UT main ping to elasticsearch index for debugging (kibana)

Categories

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

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: kparlante, Assigned: whd)

Details

We won't want these indexed forever, but one more tool for debugging during the beta period...

From:
https://ci.mozilla.org/job/mozilla-central-docs/Tree_Documentation/toolkit/components/telemetry/telemetry/main-ping.html

sessionId: <uuid>,  // random session id, shared by subsessions
subsessionId: <uuid>,  // random subsession id
previousSessionId: <uuid>, // session id of the previous session, null on first run.
previousSubsessionId: <uuid>, // subsession id of the previous subsession (even if it was in a different session),
                              // null on first run.

subsessionCounter: <number>, // the running no. of this subsession since the start of the browser session
profileSubsessionCounter: <number>, // the running no. of all subsessions for the whole profile life time

sessionStartDate: <ISO date>, // daily precision
subsessionStartDate: <ISO date>, // daily precision, ISO date in local time
subsessionLength: <number>, // the subsession length in seconds
Summary: Add the session related fields from UT main ping to kibana index for debugging → Add the session related fields from UT main ping to elasticsearch index for debugging (kibana)
This requires cracking open the Payload in the elasticsearch encoder, which means we take the JSON decode hit (should be fine for beta traffic though).
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.