Configuring the Components of a Stat Server Solution
Topic Optimizing Performance provides hardware and software recommendations addressing the number of Stat Server instances required for optimal performance.
To properly monitor a SIP cluster:
- All Stat Server nodes within the Stat Server cluster solution must be running.
- The Stat Server cluster solution must include one and only one connection to every T-Controller interface of the SIP cluster One Stat Server instance can connect to only one T-Controller interface.
- The Stat Server cluster solution must include connections to all Interaction Proxy interfaces. More than one Stat Server instance can connect to the same Interaction Proxy interface.
For example, let us assume that a particular SIP Cluster has four nodes (SIPServerA through SIPServerD) and the Stat Server solution that services this SIP Cluster contains eight Stat Server applications (StatServer1 through StatServer8). In order to maintain an even distribution of events amongst the eight Stat Server instances, each could be configured to connect to SIP Cluster components as illustrated in the figure below; namely:
- StatServer1 includes connections to T-ControllerA and IProxyA of SIPServerA
- StatServer2 includes connections to T-ControllerB and IProxyB of SIPServerB
- StatServer3 includes connections to T-ControllerC and IProxyC of SIPServerC.
- StatServer4 includes connections to T-ControllerD and IProxyD of SIPServerD.
- StatServer5 includes connection to IProxyA.
- StatServer6 includes connection to IProxyB.
- StatServer7 includes connection to IProxyC.
- StatServer8 includes connection to IProxyD.
In this configuration, call-related TEvents from each Interaction Proxy interface will be balanced among two Stat Server applications.