Closed
Bug 997449
Opened 7 years ago
Closed 7 years ago
Need response time alert for Firefox Accounts
Categories
(Cloud Services :: Operations: Metrics/Monitoring, task)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: kthiessen, Unassigned)
Details
(Whiteboard: [qa+])
We'd like for someone to be notified if the response time for FxA (account creation, log in, etc.) goes above a certain threshold. :edwong, :ckarlof, :gene, and :mostlygeek will probably all have input into this, so I'm cc'ing all of them. Please feel free to include others.
| Reporter | ||
Updated•7 years ago
|
QA Contact: kthiessen
Updated•7 years ago
|
Whiteboard: [qa+]
| Reporter | ||
Comment 1•7 years ago
|
||
Folks, is this covered by our current metrics for FxA? And do we have someone in Ops on pager duty for it? If so, I'll go ahead and close it.
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 2•7 years ago
|
||
Resolving this bug without answering the question in it leaves me no wiser than I was when I filed it. Can I at least get a snapshot of the current state of play?
Comment 3•7 years ago
|
||
boom: https://heka.fxa.us-west-2.prod.mozaws.net/#plugins/filters/FxaAuthRequestTime No notifications on the specific values but we do have monitors for latency on the servers as a whole.
| Reporter | ||
Comment 4•7 years ago
|
||
:jrgm, does this level of monitoring fit with your needs? It does not address the 'alert' in the title, but it's better than what we had.
Flags: needinfo?(jrgm)
Comment 5•7 years ago
|
||
Yeah, so if there was a measure of 90th percentile (or similar) and an alert at some multiple of that value, that would be something to have. I'm just not sure to whom to route this notification.
Flags: needinfo?(jrgm)
| Reporter | ||
Comment 6•7 years ago
|
||
No response here for 30 days means I'm marking this VERIFIED/FIXED. John, if the 90th-percentile stuff is necessary, you or I can file a follow-up bug. It looks like this one is as done as it's going to get.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•