763116 - Need to automate regular symbolication of chrome hang reports

Status: RESOLVED FIXED

(Mozilla Metrics :: Data/Backend Reports, defect)

Description

[Vladan Djeric (:vladan)]

While processing chrome hang reports from METRICS-663, I discovered that symbols for nightly builds are deleted every 30 days. We need to set up a cron job which will regularly gather Telemetry pings with chrome hang data and symbolicate the function addresses in the hang reports. I have a very simple script which can do the symbolication part.

Comment 1

[Annie Elliott]

This will be considered with the rest of the telemetry work for next quarter.

Comment 2

[(dormant account)]

(In reply to Annie Elliott from comment #1)
> This will be considered with the rest of the telemetry work for next quarter.

I'm not clear on what this means. Does this mean that we are not even considering working on this until Q3? I'm not sure what "rest of telemetry" part means. Is all telemetry work suspended until Q3?

Comment 3

[(dormant account)]

Note, we have a hard 30day window after which it will not be able to symbolicate data from older builds.

Comment 4

[(dormant account)]

Paula pointed out that we are already in Q3 :) I would still like clarification & more specific timeframes re:Annie's comment above. Note bug 764216 landed on July 18th. We will start loosing data on June 19th.

Annie, please do not remove [Snappy] whiteboard tags.

Comment 5

[Annie Elliott]

migrated to JIRA https://metrics.mozilla.com/projects/browse/METRICS-827

Comment 6

[Annie Elliott]

New JIRA migration identifier - 55 BZ issues being considered in current planning for Q3

Comment 7

[Xavier Stevens [:xstevens]]

Fixed up symbolicate.py and checked it into our telemetry-toolbox project. I also pushed it out and updated our cron job to use it going forward. In addition I did back runs for all days since June 18th (30 days ago) and the results are reflected on our server (https://metrics.mozilla.com/protected/telemetry/chrome-hangs).