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.
The following table shows a typical Verba Monitoring Plan:
Monitoring | Recommended frequency | |
HW, OS and database | Ongoing | |
Automated | Service health checks | Ongoing |
Memory monitoring | Ongoing | |
Volume monitoring | Ongoing | |
Idle monitoring | Ongoing | |
Manual | Test calls | Weekly |
Simple system inspection | Monthly |