Monitoring Yate
(Created page with "This shows the modules you need configured and loaded in order to monitor what happens in the server, especially when you have limited access to Yate (e.g. when Yate runs as d...") |
Revision as of 15:59, 16 August 2013
This shows the modules you need configured and loaded in order to monitor what happens in the server, especially when you have limited access to Yate (e.g. when Yate runs as daemon).
Meaning:
- Eventslog accessed from Rmanager
- SNMP data from Monitoring through YATE SNMP agent
Since you use or will use Yate, you'll need to check what happens inside the server at some point or another. The services Yate provides must be continuous, in order to avoid loss of calls or information (besides, who would want their lines to stop working right in the middle of a sales conference or a management meeting?).
Monitoring your system can be done in more ways than one, like many other things. This document reffers to the cases where your Yate runs as a daemon (for Linux users). This means that once it's started, you cannot communicate with it directly using a terminal.
The examples given in this document are from Mandriva 2010 spring OS, and Yate/YateClient 4.1.
