Breakpad/Status Meetings/2016-02-03: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(9 intermediate revisions by 3 users not shown)
Line 18: Line 18:


== Operations Updates ==
== Operations Updates ==
* ELB endpoint moved on stage and prod?
** https://github.com/mozilla/socorro-infra/pull/228
** problem was with HTTPS redirects
* How the hosted ES moving coming along?
** https://bugzilla.mozilla.org/show_bug.cgi?id=1239365
** turns out security is different, we can't but it inside our VPC (firewall), we can't do it by IP address. Need to sign our requests (reads/writes) with an AWS key.
** might be able to set up an NAS to route as if all the ES queries come from predictable IPs.
** Next actions: jp to talk to AWS about possible solutions. Plan B; adrian to write some code to extend queries.


== Project Updates ==
== Project Updates ==
Google Analytics Content Drilldown:
* Google Analytics Content Drilldown:
* 44.1% - /report/index/
** 44.1% - /report/index/
* 13.5% - /home/products/Firefox
** 13.5% - /home/products/Firefox
* 13.4% - /topcrashers/
** 13.4% - /topcrashers/
*  9.8% - /report/list
**  9.8% - /report/list
*  8.1% - /search/
**  8.1% - /search/
*  2.3% - /signature/
**  2.3% - /signature/
*  1.6% - /crashes-per-day/ (adjusted for redirect)
**  1.6% - /crashes-per-day/ (adjusted for redirect)
*  0.2% - /status/
**  0.2% - /status/
 
* Can WebQA start monitor and measure the SuperSearch API?
* ujson or simplejson or json?
** parsing 282 .json files, totalling 25Mb
*** ujson is 3.8 times faster than simplejson and (built-in) json
*** simplejson uses ~61.5Mb of RAM, ujson ~84Mb, json ~76Mb
* Super Search API documentation is released!
** https://crash-stats.mozilla.com/documentation/supersearch/
* found a bug with PolyCrashStorage while working on the new ES cluster [adrian]
** https://bugzilla.mozilla.org/show_bug.cgi?id=1245558


=== Deployment Triage ===
=== Deployment Triage ===
Line 40: Line 56:


== Travel, etc ==
== Travel, etc ==
* Lars
**  PyTN - out THU 2/04 - WED 2/10
* mbrandt - 02/05 - 02/08 - backcountry hut trip


== Links ==
== Links ==

Latest revision as of 19:09, 3 February 2016

« previous meeting — index – next week » create?

Meeting Info

Breakpad status meetings occur on Wed at 11:00am Pacific Time.

Conference numbers: 

   Vidyo: Stability 
   650-903-0800 x92 conf 98200#
   800-707-2533 (pin 369) conf 98200#

IRC backchannel: #breakpad
Mountain View: Dancing Baby (3rd floor)

Operations Updates

  • ELB endpoint moved on stage and prod?
  • How the hosted ES moving coming along?
    • https://bugzilla.mozilla.org/show_bug.cgi?id=1239365
    • turns out security is different, we can't but it inside our VPC (firewall), we can't do it by IP address. Need to sign our requests (reads/writes) with an AWS key.
    • might be able to set up an NAS to route as if all the ES queries come from predictable IPs.
    • Next actions: jp to talk to AWS about possible solutions. Plan B; adrian to write some code to extend queries.

Project Updates

  • Google Analytics Content Drilldown:
    • 44.1% - /report/index/
    • 13.5% - /home/products/Firefox
    • 13.4% - /topcrashers/
    • 9.8% - /report/list
    • 8.1% - /search/
    • 2.3% - /signature/
    • 1.6% - /crashes-per-day/ (adjusted for redirect)
    • 0.2% - /status/
  • Can WebQA start monitor and measure the SuperSearch API?
  • ujson or simplejson or json?
    • parsing 282 .json files, totalling 25Mb
      • ujson is 3.8 times faster than simplejson and (built-in) json
      • simplejson uses ~61.5Mb of RAM, ujson ~84Mb, json ~76Mb
  • Super Search API documentation is released!
  • found a bug with PolyCrashStorage while working on the new ES cluster [adrian]

Deployment Triage

PR Triage

other business

Travel, etc

  • Lars
    • PyTN - out THU 2/04 - WED 2/10
  • mbrandt - 02/05 - 02/08 - backcountry hut trip

Links

Retrieved from "https://wiki.allizom.org/index.php?title=Breakpad/Status_Meetings/2016-02-03&oldid=1115757"