105
edits
Community Ops/Monitoring: Difference between revisions
Jump to navigation
Jump to search
First draft
(First draft) |
|||
| Line 1: | Line 1: | ||
{{draft}} | |||
==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:''' | |||
* New Relic - Watches server statistics, allows us to ensure great performance and stability of our servi es | |||
* Uptime Robot - 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. | |||
==Services== | |||
=== New Services === | |||
[[File:Monitoring New Services.jpg]] | |||
=== Existing Services === | |||
{| class="wikitable" | |||
|- | |||
! Service !! Details !! Monitoring Configuration !! Bug | |||
|- | |||
| Discourse || http://discourse.mozilla-community.org || Don't know || 123456789 | |||
|- | |||
| Example || Example || Example || Bug | |||
|- | |||
| Example || Example || Example | |||
|} | |||