Loop/Test/Monitoring

From MozillaWiki
< Loop‎ | Test
Jump to: navigation, search

Overview

The purpose of this wiki is to provide a reference of monitoring tools for both test and production environments. Typically monitoring would only be performed where a load is present.


This page will include some information about analysis (i.e. log analysis) as well.


#top


Monitoring Tools (STAGE)

Loadtest (loadv1) Test Dashboard


#toc


Sentry:


#toc


Stackdriver:


#toc


Graphite


#toc


Kibana


#toc


Heka


#toc


Monitoring Tools (PRODUCTION)

Sentry


#top


Stackdriver


#top


Kibana



#top


Heka


#top


loop-server Dashboard


#top


Graphite:


#top


Firefox Input Dashboard:


#top


Pingdom:


#top



Log Monitoring

Tail multiple logs 

$ cd /media/ephemeral0/nginx/logs
$ tail -f loop_server.access.log loop_server.error.log  default.access.log default.error.log

Other logs of interest:
For example, for loop-server:

  • /var/log/circus.log
  • /var/log/loop_err.log
  • /var/log/loop_out.log
  • /var/log/hekad/loop.stdout.log
  • /var/log/hekad/loop.stderr.log
  • /var/log/nginx/access.log
  • /var/log/nginx/error.log


#top


HTTP Access Log - Parsing

unique REST activity with counts 

$ cat /media/ephemeral0/nginx/logs/loop_server.access.log | grep "HTTP/" | awk '{print $6" "$3" "}' | sort | uniq -c


unique REST activity with counts (from a .gz file) 

$ zgrep -a "HTTP/"  /media/ephemeral0/nginx/logs/loop_server.access.log-20150114.gz |  awk '{print $6" "$3" "}' | sort | uniq -c


return only the interesting stuff 

$ cat loop_server.access.log | grep -v '200 ' | grep -v '101 ' | grep -v '499 ' | grep -v '201 ' | grep -v '204 '


#toc

Retrieved from "https://wiki.mozilla.org/index.php?title=Loop/Test/Monitoring&oldid=1075924"