Introducing monitoring procedures

Verba solutions depend on a number of external factors that might cause degradation of the recording, replay and archiving functionality:

Server hardware failures
Operating system failures or configuration errors
Network failures or configuration errors (both access and traffic spanning related)
Database server problems
Storage network failures
System overload

The Verba Call Recording System is built to provide call recording and replay functionality around the clock.
Verba Technologies constantly improves the reliability of Verba software and builds active monitoring and automatic intervention solutions to cope with failure situations due to software and other external problems.

In this topic the monitoring and maintenance best practices are summarized that will help you operate Verba safely.

This topic does not deal with regular hardware, operating system and database monitoring and maintenance procedures. Your IT organization should take care of those parts according to respective product documentation or your existing processes.

We recommend designing and introducing monitoring procedures based on this article to ensure that problems are detected as early as possible to minimize downtime.

The following table shows a typical Verba Monitoring Plan:

Monitoring procedure		Recommended frequency
HW, OS and database (not detailed here)		Ongoing
Automated monitoring functions in Verba	Service health checks	Ongoing
	Memory monitoring	Ongoing
	Volume monitoring	Ongoing
	Idle monitoring	Ongoing
Manual monitoring procedures for Verba	Test calls	Weekly (if security policies does not allow listening to actual recorded calls)
Manual monitoring procedures for Verba	Simple system inspection	Monthly