Closed Bug 698799 Opened 14 years ago Closed 14 years ago

Add statsd and start tracking things

Categories

(Input Graveyard :: Backend, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: davedash, Assigned: davedash)

References

()

Details

(Whiteboard: [es])

Before we flip to ElasticSearch, we need to start tracking data. This bug entails: - setting up statsd in input - tracking various things (for example): - search 500 errors - pagination clicks - filters - raw searches to sphinx - setting up potch's statsd toy When we switch to statsd we can start seeing success and failures and dialing knobs accordingly. CCing James, in case he has other ideas of what to track.
commonware has two very useful Statsd/Graphite middleware bits: commonware.response.middleware.GraphiteMiddleware - simply increments counters for all your HTTP status codes commonware.response.middleware.GraphiteRequestTimingMiddleware - times all views, separated by HTTP method It would be interesting to write some kind of decorator that would log a specific view's non-2xx/3xx responses. Setting up statsd most likely just means opening some network routes. [1] https://github.com/jsocol/commonware/blob/master/commonware/response/middleware.py#L56
> It would be interesting to write some kind of decorator that would log a > specific view's non-2xx/3xx responses. @statsd.errors # <-- better name? def myview(): and then it uses the package/function name to come up with the key? e.g. input_error_search_myview?
mbrandt, you know how statsd works.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: Input → Input Graveyard
You need to log in before you can comment on or make changes to this bug.