2013-07-26 analytics team raw meeting notes

[09:03:38] <patrickdsouza>
http://docs.webplatform.org/wiki/WPD:Community/Meetings/Analytics

[09:04:00] <julee>  Analytics Meeting started

[09:04:19] <julee>  with julee, patrickdsouza and renoirb

[09:04:39] <julee> renoirb is new devops

[09:05:39] <julee> patrickdsouza : top priority 503s

[09:05:52] <julee>  Šwe need to install it on its own box to resolve this

[09:06:15] <julee> renoirb : specific to host the piwik app

[09:06:34] <julee>  Šalso whatever happens, it shouldn't fail the rest of
the site

[09:06:56] <julee> renoirb doesn't have access to fastly, just the server
themselves

[09:07:14] <julee> patrickdsouza : fastly has the api, so we can see the
historical data

[09:08:12] <julee>  Šcomparing the number of hits in fastly vs. piwik. all
our page hits go thru fastly so we don't know if piwik #s are right

[09:08:24] <julee>  Šwe need to compare the 2 data sets

[09:08:49] <julee>  Šso we need an api key

[09:09:36] <julee>  julee : 1600 hits a day, for the past 6 months. really
suspiciously consistent and low

[09:09:56] <julee>  AI : renoirb will get access to fastly & their api

[09:10:29] <julee>  AI : renoirb will get piwik on its own instance

[09:10:41] <patrickdsouza>  latest version of piwik on its own instance

[09:11:17] <julee>  patrick : we aren't tracking www. shepazu was looking
into it

[09:11:28] <julee>  AI: shepazu status on tracking on www?

[09:12:20] <patrickdsouza>  2 - web cluster 1- blog 1- piwik

[09:12:23] <julee>  patrick : 2 instances for web cluster, 1 instance for
blog, 1 for piwik

[09:12:42] <julee> renoirb : we're thinking of switching to word genix <sp?>

[09:13:06] <patrickdsouza>  nginx

[09:13:24] <julee>  Š an http server instead of apache1

[09:14:04] <julee>  Šnginx also does caching. We could send to fastly, then
if fastly fails, we still have a cache

[09:14:19] <patrickdsouza>  nginx is a better option than apache

[09:14:25] <patrickdsouza> wordpress.com <http://wordpress.com/>  runs on
nginx

[09:14:27] eliezerb (~eliezerb@179.206.48.175) left IRC. (Read error:
Connection reset by peer)

[09:14:38] <julee> renoirb : try it on a 2nd machine w/ ghost host subdomain
to test, with wordpress, for example

[09:14:52] <renoirb>  yes

[09:15:15] <julee>  julee : nginx can we do it with piwik first?

[09:15:23] <julee>  all : yes

[09:15:45] <julee> patrickdsouza has been using it w/ good results

[09:16:12] <julee> renoirb : create the front end, and nginx can do load
balancing, proxying, everything

[09:16:44] <julee>  Š in the future, we have a collection of IP addresses,
ea is an nginx front end, with an app server behind it

[09:16:46] <patrickdsouza>  latest version of nginx has support for
websockets etc

[09:16:55] <julee>  Š the load is managed by the frontend server

[09:16:59] <julee>  Š lowers the cost

[09:17:25] <julee> patrickdsouza : start with piwik

[09:17:41] <julee>  Š the latest version of piwik

[09:17:48] <julee>  ...

[09:17:56] <patrickdsouza>  piwik, nginx, fastcgi and apc combination

[09:18:25] <renoirb>  HipHop VM

[09:18:41] <renoirb>  could be overkill at the moment

[09:18:44] <julee> patrickdsouza : apc or hiphop, try either one

[09:18:57] <julee>  Š not sure about hiphop

[09:19:13] <patrickdsouza>  lets try hiphop else we'll use apc

[09:19:24] <julee> renoirb : facebook -- fastest possible

[09:19:26] <renoirb>  so try Piwik with NGINX + APC caching first

[09:19:33] <renoirb>  so far.

[09:19:50] eliezerb (~eliezerb@179.206.48.175) joined the channel.

[09:20:28] <julee>  AI : renoirb will follow up w/ Ryan & shepazu.

[09:20:50] <julee>  make sure to get fastly access

[09:20:58] <julee>  get latest piwik instance

[09:21:32] <julee>  try nginx & caching, with proper config - if http fails,
monitor & make sure it doesn't break everything else

[09:21:43] <renoirb>  AI: Piwik configure in a way to ensure it doesn't
break

[09:21:51] <julee>  julee : wordpress version is behind as well

[09:21:55] <renoirb>  AI: Update WordPress with NGINX as well

[09:22:46] <patrickdsouza>  wordpress 3.6 should be out soon in the next
month or two

[09:22:55] <patrickdsouza>
http://wordpress.org/news/2013/07/wordpress-3-6-release-candidate-2/

[09:23:17] <julee> renoirb ; still 503s

[09:23:19] <julee>  ?

[09:23:45] <julee>  ryan reduced processes.

[09:23:58] <renoirb> aremysitesup.com <http://aremysitesup.com/>

[09:24:20] <julee> renoirb : we may not know when it fails. Maybe a small
account on aremysitesup , infrastructure & our own monitoring down the road

[09:24:39] <renoirb>  cheap quick way to monitor until we get our own
monitoring

[09:24:43] <julee>  AI: renoirb : do a quick aremysitesup account

[09:25:15] <julee>  AI: renoirb will get more information about monitoring
from Ryan_Lane

[09:25:58] <julee>  priority is piwik instance, then nginx, the wordpress

[09:26:45] <julee> renoirb : but this infrastructure stuff isn't in the
scope of this meeting

[09:26:58] <renoirb>  Fix on priorities:   AreMySitesUp, Then NGINX for
Piwik, then Wordpress USINg piwik

[09:27:05] <renoirb>  NGINX

[09:27:09] <julee>  all : yes, just became a topic of discussion because
piwik is the culprit

[09:27:21] shepazutoo (~shepazuto@67.23.204.2) joined the channel.

[09:27:46] <julee> patrickdsouza : renoirb, can you get access to fastly?

[09:27:57] <julee> renoirb : yes, a priority

[09:28:04] <renoirb>  AI: Grant renoirb access to Fastly

[09:28:42] eliezerb (~eliezerb@179.206.48.175) left IRC. (Read error:
Connection reset by peer)

[09:29:26] <julee> http://project.webplatform.org/analytics/issues/open

[09:29:53] <julee> patrickdsouza : going to do a wireframe of the dashboard

[09:30:11] patrickdsouza (~patrick@c-76-116-66-203.hsd1.nj.comcast.net) left
IRC. (Ping timeout: 256 seconds)

[09:30:19] <julee>  Š and will pull a set of requirements out of that UX
wireframe

[09:30:54] <julee>  julee : dependencies: cron jobs

[09:31:18] <julee>  patrickdsouza : send data to piwik

[09:31:22] patrickdsouza (~patrick@c-76-116-66-203.hsd1.nj.comcast.net)
joined the channel.

[09:31:47] <julee> patrickdsouza : we don't have one first, but we need one

[09:32:08] <julee>  Š so piwik can hold the data

[09:32:28] <julee>  Š and the dashboard will be at piwik as well

[09:32:29] leaverou (~leaverou@ppp-94-64-6-232.home.otenet.gr) joined the
channel.

[09:32:32] <patrickdsouza> http://project.webplatform.org/analytics/issues/5

[09:32:51] <patrickdsouza> http://project.webplatform.org/analytics/issues/3

[09:33:17] <julee> patrickdsouza : look at issue #3

[09:33:50] leaverou  there is a call today? I thought we weren't having one
from the mailing list discussion

[09:34:04] <patrickdsouza>  analytics call

[09:34:11] <julee>  Hi, leaverou! No general meeting.

[09:34:26] <renoirb>  yes, we are. At least for the action items to improve
the system problems

[09:34:28] <julee>  Analytics team usurped the hour

[09:34:38] <leaverou>  ah, ok

[09:35:46] <julee>  julee : piwik is slow

[09:36:01] <julee> patrickdsouza : auto-archiving. should be disabled

[09:36:24] <julee> renoirb : probably there are some improvements we can
make as well

[09:36:33] Reedy (~quassel@wikimedia/pdpc.active.reedy) left IRC. (Ping
timeout: 260 seconds)

[09:36:40] <patrickdsouza>  mysql storage engine

[09:36:47] <patrickdsouza>  Innodb or MyISAM

[09:36:47] <julee> patrickdsouza : makes a difference

[09:37:05] <julee> renoirb : looking at the server...

[09:37:12] <patrickdsouza>  if we are using the latest version of mysql then
it should be innodb by default

[09:37:17] <julee>  Š needs db access

[09:38:26] <julee>  julee : we need a cron job for the sitemap

[09:38:38] <patrickdsouza> http://project.webplatform.org/analytics/issues/6

[09:38:50] <patrickdsouza>  tickets assigned to denis should get assigned to
renior

[09:38:55] <julee>  All the tix assigned to denis should probably go to
renoirb.

[09:39:32] <julee>  AI : renoirb to follow up on bugs assigned to Denis

[09:41:00] <julee>  julee : sitemap jqxhr I'm doing is really slow

[09:41:11] <julee>  patrikdsouza : build it at the time of the cron job

[09:41:13] <patrickdsouza>  create a static file as a part of the cron xml
process

[09:41:26] <Garbee> renoirb, The fastly API key is in /root/fastly-api.key

[09:41:32] <julee>  julee : sorting on the page is taking a long time.

[09:41:34] <Garbee>  sudo vim /root/fastly-api.key will show it to ya.

[09:41:54] <renoirb>  from deployment host?

[09:41:55] <Garbee>  ^^Response from at the beginning when you mentioned
needing it.

[09:41:58] <Garbee>  Yea

[09:42:01] <renoirb>  ok :)

[09:43:52] eliezerb (~eliezerb@179.206.48.175) joined the channel.

[09:44:28] <julee> patrickdsouza : maybe a separate json file to manage
sorting & nav of the 4500 items

[09:44:49] <julee>  julee : will try with item renderers

[09:45:49] <julee>  AI: julee to re-write code & then modify issues 6 to
include writing to an html file & json as part of the cron job

[09:48:20] shepazutoo (~shepazuto@67.23.204.2) left IRC. (Quit: shepazutoo)

[09:51:14] <patrickdsouza>  we can separate xml files for each level of the
hierarchy

[09:51:22] <patrickdsouza>  *we can create separate xml files

[09:59:38] <renoirb>  Monday 19:00 EST

[09:59:43] <renoirb>  Zulu -5

[10:00:03] <renoirb>  August 5th

[10:00:03] <julee>  starting 8/5

[10:00:22] <renoirb>  thanks Garbee, I grabbed it :)

[10:00:23] <julee>  AI: julee to confirm w/ shepazu that he can do that
time.

[10:00:47] <julee>  meeting over



----------------------------
julee@adobe.com
@adobejulee

Received on Friday, 26 July 2013 17:02:53 UTC