866942 - Ponder the payments flow for statsd logging

Status: RESOLVED FIXED

(Marketplace Graveyard :: Payments/Refunds, defect, P3)

Description

[Kumar McMillan [:kumar]]

We collect statsd logging to monitor realtime stability and performance. This bug is to:

1) Close your email, IRC, and other things that distract :)
2) Step through the entire payments flow (and code) from a technical perspective
3) Write down all parts that could use statsd logging. A useful statsd measurement is one that will tell us if some part of the system is failing or suspicious
4) Add statsd logging for each one

Comment 1

[Andy McKay]

And some nice graphs in the dashboard would be nice.

Comment 2

[Andy McKay]

Solitude logs lots to statsd. Adding in statsd to curling and webpay:

https://github.com/mozilla/webpay/commit/d4cbd1

Comment 3

[Andy McKay]

We've got all incoming requests being timed and reporting status codes. All outgoing requests (and those via curling are timed).

https://github.com/andymckay/curling/commit/9ab9ee

Someone now needs to do some meaningful graphs.