Monitoring a replica server

Proactive monitoring of the replica server occurs via email. The TeamForge web interface displays recent command history including the commands that are scheduled to run, the status of the ones actively running and the ones that failed. For current jobs, there are links to the runtime output.

Active monitoring

Configuring the mail server information in the Subversion Edge replica turns on active monitoring. For more information, see Configure the mail server. The replication process sends emails when an event fails. For example, if svnsync is running and the network drops, the retries are exhausted or not turned on and the command fails. An email is sent to the address configured in Subversion Edge — this can be a group address or mailing list. The email contains the same information as the log. This includes the error information in the output of the svnsync command as well as an internal stack trace.

Passive monitoring

The TeamForge web interface provides monitoring information. At the site level, you can see the status of the entire replica server and queue including the event actively being processed. You can also see this at the repository level from within a TeamForge project. For more information, see Check command history in TeamForge.

There are basic summary icons to show status. For more information, see Replica status icons. A cloud icon indicates a problem in the recent events and you can click it to see the details.

Usage monitoring

As with Subversion on a master server, the way to measure the usage of the replica server is via the logging. The replicas have both Apache access logging and Subversion command logging. You can create usage reports from these log files to find out how much activity is being serviced by the replica server.