Community Ops/Monitoring: Difference between revisions

Revision as of 17:17, 31 August 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 is decentralized. Incident Response is distributed based on timezone, availability and project knowledge.

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.

Service	Details	Monitoring Configuration	Bug
Discourse	http://discourse.mozilla-community.org	Don't know	123456789
Example	Example	Example	Bug
Example	Example	Example

@@ Line 1: / Line 1: @@
-Draft Community Ops/Monitoring
+{{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
+|}