Does anyone know if there is any sort of maximum capacity for Filters in the StatServer? I’m thinking of adding a couple of hundred(!) for use in CCPulse+ (for real-time only - not historical)
Has anyone hit a ceiling in this area?
Ta,
Tony
Tony,
I don’t think the number of filters makes any difference. The number of calculated/collected stats - this what you’ve got to watch out. Even in case of a high number of stats, stat server will run fine as long as hardware that it’s installed on can handle it. I have seen a document in Genesys Library/Tech Support site regarding hardware sizing and how to calculate the requirements based on a number of statistics configured within stat server.
On a side note, you would probably need a good PC anyway to run CCPulse client to handle all of those stats/filters 
Alex.
1 Like
We are using a crazy number of filters here, there doesnt seem to be any detrimental effect.
Mark
2 Likes
Mark, what’s crazy? Couple hundreds? Just for my reference.
Filters are loaded when StatServer starts, then if no stat uses it, it will remain sleep. What I will consider is the number of statistics created and customer/applications connecting to each statserver
OK - let’s say I need to add in 300 Filters. Then I need to create a Virtual Queue View/Template showing calls Entering, Distributed and Answered, with and without each Filter. …and there are about 300 Virtual Queues. …and the StatServer still needs to feed all other current CCPulse+ stat requests…
That’s definitely gonna stuff up the StatServer - right?
Sorry - I think I just answered my own question…
Tony
You will need to consider time profiles, time ranges, interval types, etc those kind of details
1 Like
At a quick count, there are around 300-400. In my last place of work there was also a similar amount!
1 Like