We're starting to get asked to do ad-hoc querying of these logs more frequently, so we should grant some additional folks access to them. Specifically: email@example.com firstname.lastname@example.org email@example.com firstname.lastname@example.org email@example.com firstname.lastname@example.org email@example.com It would be great if we could turn on Athena for everybody too (all above + me, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org), since that seems like it would be better than mounting an s3 volume. RelEng folks - https://wiki.mozilla.org/Balrog#ELB_Logs talks a bit about parsing these logs, if you end up doing it.
Hey Benson, This is blocking release work in bug 1329692. Would you be able to help us with access? Having everyone Ben listed would be ideal but, if it helps, we could focus on email@example.com, firstname.lastname@example.org, and email@example.com. These 3 are the folks who are currently managing releases in flight. thanks!
Created the accounts. Will ping jlund to distribute credentials.
Regarding Athena. I set up a Athena table and ran a really simple query over 1 day worth of logs. It took a long time and transferred about 1.5TB ($7.50) to do a single day. We're going to be evaluating how to optimize this for both speed and cost.
What's the status here folks? This bug has been idle for a week. We have users stranded on 47 right now we would like to get updated.
Sorry for the delay. We have been a bit busy with the current release and related work...
(In reply to Jim Mathies [:jimm] from comment #4) > What's the status here folks? This bug has been idle for a week. We have > users stranded on 47 right now we would like to get updated. To be clear: the folks that need it now have access to these logs. This bug has remained open to track enabling Athena for Balrog logs. It might be worth filing a separate bug about the specific analysis that needs to be done to unblock bug 1329692.
Delay is on me. As rail mentioned, release and migrations have taken priority recently. I will raise this today at release meeting. I'll also file a separate bug to track the specific analysis
Status: NEW → RESOLVED
Last Resolved: 10 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.