You can query for the last error, or also get notified with one or two messages when errors occur (instead of a big email flood).Ĭanook: 4 error(s) on at. Arecibo We are sending errors to Arecibo which puts the errors into a database where they can be stored and priortised. You can ask it how HTTP responses of a certain status code are happening, or it will tell you when it goes over a threshold:Ĭanook: 403 status: 3.19/sec average over the last 15 mins. I wrote one using phenny: Graphite This parses graphite, which is populated by statsd, so we can spot when something goes wrong on the site. Gk0bes: Pushed by kumar303 pushbot Connects to redis and tells us how a push to the production server is going. There's some bots built by the team, Jeff Balogh wrote a couple using node.js: amobot This tells us a couple of things: 1) when someone commits something to master and 2) the difference between the staging server and head (for when something gets stuck going to the stage server). It tells us when the basic monitoring has a problem: Nagios We don't actually use this in AMO, but the SUMO team do. Because the commit includes the bug number, firebot pipes up. That's Jenkins telling me the build is broken (it's not actually my fault for a change) and telling us what commit it was. , 6.1.8, amckay, NEW, Add mobile strings to API for language packs Hudson: Andy McKay: add in get_localepicker (bug 674253) Hudson: Project amo-master-js build #928: STILL UNSTABLE It's especially nice when it works with Firebot. It will tell us when builds fail or pass and allow us to start new builds etc. P4, 6.1.6, amckay, RESO FIXED, Add an API point to accept performance data Jenkins This bot allows us to interact with Jenkins. It actually does an awful lot of different things, but we currently just get information on bug Firebot Firebot (or Mozbot) interacts with Bugzilla, for us. Here's an overview of the bots used and what they do. We've got quite a few bots for AMO, so we moved them all to a new channel, #amo-bots, because it was getting quite distracting. With IRC, it's easy to write bots that communicate with users or a channel. Yet with its simple protocol and large number of clients and libraries, IRC persists. It seems every year someone comes out with some new innovate way of chatting to groups, to overcome perceived shortcomings elsewhere. We use IRC all day long for pretty much everything. Like the rest of Mozilla, the team that works on (AMO) use IRC.
0 Comments
Leave a Reply. |