Templates and Examples - The Practice of Cloud System Administration - page 478

be named bosun01.example.com. It will be in the Phoenix and Toronto datacen-
ters. Monitoring configuration will be kept in the Git “sysadmin configs” repo, in
the top-level directory /monitor .
Detailed Design:
Server configuration:
Dell 720XD with 64G RAM, 8 disks in RAID6 configuration
Debian Linux (standard corporate “server configuration”)
Bosun package name is “bosun-server.”
• Any system being monitored will have the “bosun-client” package installed.
• Backups will be performed nightly using the standard corporate backup mech-
anism.
• (The full document would include a description of operational tasks such as
adding new monitoring collectors, and alerting rules.)
Cost Projections:
• Initial cost [cost of server].
• Software is open source.
• One half-time FTE for 3 weeks to set up monitoring and launch.
Schedule after approval:
1. 1 week to procure hardware.
2. 2 days of installation and testing.
3. “Go live” on week 3.
Alternatives Considered:
Zappix and SkunkStorm were both considered, but the feature set of Bosun is
more closely aligned with the project goals. [link to comparison charts]
Special Constraints:
Bosun stores SNMP “community strings,” which are essentially passwords, in a
password vault. The storage method has been reviewed and approved by Security
Operations.
D.3 Sample Postmortem Template
Below is a simple postmortem template as described in Section 14.3.2 .