Difference between revisions of "SystemMonitoringDashboard"
| Line 22: | Line 22: | ||
* Implement monitoring | * Implement monitoring | ||
| + | |||
| + | == List of items to monitor == | ||
| + | |||
| + | * Lucene | ||
| + | * RAID array status | ||
| + | * Disk space | ||
| + | * Apache | ||
| + | * MySQL & replication | ||
[[Category:DevelopmentTeamTask]] | [[Category:DevelopmentTeamTask]] | ||
Revision as of 07:13, 31 August 2007
What (summary)
Servers and some services are currently being monitored by Name Intelligence, but we would like to implement extended host, service, and network monitoring. This should help us keep a better eye on the running infrastructure and make us more quickly aware of potential issues.
Why this is important
We need to be aware of issues as soon as possible. This will provide more visibility to the environment.
DoneDone
- We know when Lucene is working/not working (monitoring of Lucene)
Steps to get to DoneDone
- Decide on monitoring solution.
- Nagios - Quite extensible. I have quite a bit of experience working with Nagios.
- Zabbix - Evaluating Zabbix on another project.
- Zenoss - Uses Nagios for monitoring, but also includes hardware inventory and performance monitoring.
- Implement monitoring
List of items to monitor
- Lucene
- RAID array status
- Disk space
- Apache
- MySQL & replication
