Community Ops/Monitoring: Difference between revisions
Jump to navigation
Jump to search
(→Monitoring: update victorops) |
|||
| Line 24: | Line 24: | ||
| Pingdom || Uptime and latency monitoring || [https://mozillians.org/en-US/u/mrz mrz] | | Pingdom || Uptime and latency monitoring || [https://mozillians.org/en-US/u/mrz mrz] | ||
|- | |- | ||
| VictorOps || Incident Escalation and notifications || tanner || [https://mozillians.org/en-US/u/mrz mrz] | | VictorOps || Incident Escalation and notifications || tanner || [https://mozillians.org/en-US/u/mrz mrz], logan, yousef | ||
|- | |- | ||
| Cloudwatch || Top Level Monitoring of AWS || Same as AWS | | Cloudwatch || Top Level Monitoring of AWS || Same as AWS | ||
Latest revision as of 19:07, 23 October 2015
|
THIS PAGE IS A WORKING DRAFT | 
|
| The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly. If you have any questions or ideas, please add them as a new topic on the discussion page. |
Monitoring Setup
General
Monitoring is decentralized. Incident Response is distributed based on timezone, availability and project knowledge.
Tools
We use a number of services to maintain effective monitoring:
- Pingdom - Checks that our servers are up. Screams if they aren't.
- VictorOps - Incident Response Management. Dispatches alerts to sysadmins and compiles a nice timeline for us to manage incidents.
How to use it
TBD
How to request monitoring
TBD
Monitoring
| Tool | Usage | Primary Contact | Secondary Contacts |
|---|---|---|---|
| Pingdom | Uptime and latency monitoring | mrz | |
| VictorOps | Incident Escalation and notifications | tanner | mrz, logan, yousef |
| Cloudwatch | Top Level Monitoring of AWS | Same as AWS | |
| StatusHub | Dashboard | mrz |