712854 - metrics for balrog

Status: RESOLVED FIXED

(Release Engineering Graveyard :: Applications: Balrog (backend), defect, P3)

Description

[[e-mail] (:bhearsum)]

Haven't really thought much about this yet, but wanted to file so it's not forgotten:
22:04 <@catlee-away> have you thought about metrics for balrog at all?
22:05 < bhearsum|afk> can't say that i have
22:05 <@catlee-away> could be nice to have counts / times for various bits
22:06 < bhearsum|afk> call counts/times for various methods?
22:07 <@catlee-away> yeah
22:07 <@catlee-away> also, how many times various rules are hit
22:08 < bhearsum|afk> ahhh
22:08  * bhearsum|afk files a bug before it slips his mind
22:08 <@catlee-away> easy to go completely overboard
22:09 < bhearsum|afk> probably need to have a conversation with Metrics at some point, too
22:09 < bhearsum|afk> i hear they like to monitor our AUS requests

Comment 1

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

found in triage.

Comment 2

[[e-mail] (:bhearsum)]

Services has a thing called "metlog" as part of the Sagrada framework. I spoke with someone about it last week and he gave me the impression that it was something that could be plugged into non-sagrada things too. There's some repositories related to it here: https://github.com/mozilla-services/ and a wiki page here: https://wiki.mozilla.org/Services/Sagrada/Metlog.

Comment 3

[[e-mail] (:bhearsum)]

mass component change

Comment 4

[[e-mail] (:bhearsum)]

I'm calling this fixed because we have a lot of stuff in Datadog now. I think we probably still want some app-specific metrics at some point, but we should file them as specific bugs.