Genesys CTI User Forum

Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: Shooter on June 09, 2016, 09:24:17 AM

Title: Stat Servers- Reporting Vs Routing
Post by: Shooter on June 09, 2016, 09:24:17 AM
What is the difference between Routing Stat Server and Reporting Stat Server, in terms of their functionality and usage?
Can we use only one stat server for both the purposes i.e. reporting and routing?
Title: Re: Stat Servers- Reporting Vs Routing
Post by: hsujdik on June 09, 2016, 11:52:53 AM
It is not impossible, though it is highly recommended to split for means of less loading on them
Title: Re: Stat Servers- Reporting Vs Routing
Post by: cavagnaro on June 09, 2016, 01:31:24 PM
Technically there is no difference only as the name suggests what they are intended to do.
Routing usually is used only by URS as you need fast and reliable info to do routing.
Reporting is usually filled with a lot of metrics, filters and lot of clients which can affect its response time.
You don't want a StatServer slow for URS.
However if you env is small,yeah you could use both but doesn't harm to be ready and avoid issues by having them splitted in two or more.

Enviado de meu E6633 usando Tapatalk

Title: Re: Stat Servers- Reporting Vs Routing
Post by: Dionysis on June 09, 2016, 01:51:34 PM
Separating them also means you can restart the routing ones without resetting everyone's CCPulse stats to 0. ;)

Title: Re: Stat Servers- Reporting Vs Routing
Post by: Adam G on June 10, 2016, 11:17:34 AM
Dionysis is spot on - avoid sharing your configuration/framework, routing and reporting solution elements.  You don't want to have to stop the whole Platform from working just because CCPulse isn't showing the right stats!  Generally, you should house Config, Framework and Solution Applications on separate Servers, too... just in case a reboot is required.