Pulse plugin

[Gaia]

Hello,

I am testing pulse plugin for GAX, I would know if someone had already tested one pulse plugin with 2 pulse collectors ( one per tenant ). 

When I lunch 2 collectors only one of them works ( the one started first).

Thank you for the help

BR,

[cavagnaro]

1 Pulse with 2 sources??? Why? How would it know from whom to request data?
Why not 2 Pulse?

[Gaia]

I found this in genesys documentation "Each Pulse plug-in can render the statistics and views across all Pulse Collectors in a cluster. " but havn't really understand it

[cavagnaro]

Cluster is a pool of applications with same config. For example, you use a Cluster os Email Servers so if one goes down the others can keep providing services.

[Gaia]

thank you , so one pluse for one collector 

[cavagnaro]

Yup.

[JohnRamella]

With the new .103 version of Pulse/Collector - you *can* have multiple Collector/Stat Server pairs feed a single instance of GAX each pointing to a separate tenant(s). You then divide the "views" in GAX w/ tenant specific users.

[Dionysis]

Yes you can have multiple collectors per pulse instance.  But I wouldn't recommend the 8.5.103.x version, go direct to 8.5.104.x, there are a lot of UI glitches 8.5.103.x versions. 

[Gaia]

hi,

yes I have problems with this version 8.5.103.05 plugin enabled but cannot see it in GAX.

I cannot see 8.5.104.x in genesys software downloads ,  when it is released ?

Br,

[Dionysis]

Apologies, I was looking at the collector version.  It's 8.5.103.05 of GAX that I'm running, and the 8.5.103.03 that I had problems with.  It wasn't anything to do with not being able to see Pulse though, it was issues with the interface itself when using Pulse.

I have other issues with multiple collectors though, if using 1 collector and 1 pulse it works fine, but does not split across multiple collectors like it should.  I've also got issues where each of my GAX instances show different dashboards for the same user... so much for the new clustered deployment model.  I'm raising this with Genesys support though, it will be my 6th ticket on deploying Pulse / Pulse Collector and I still don't have it running in production.  *insert jaded rant on Genesys quality control here*

[cavagnaro]

I have like 20 already opened and after 10th decided will look at it again only in a year from now. Perda de tempo. CCPulse still in my heart.

[Dionysis]

I thought that about a year ago Cav, but now I'm getting pressure from customers to get it up and running because they've heard about it from Genesys, in theory it should be a good solution... I was amazed at the problems in the 8.5.103.03 version of Pulse, there is just no way it was tested before release.  It took me about 30 seconds after installing it to find issues with the interface that made it completely unusable.

[cavagnaro]

You know how to postpone it? What I have done, install and show them pair to pair vs a CCPULSE.
Then I grab the most wanted metric, current calls ir current agents on some state.
Result: Ccpulse is real current status.
Pulse...you wait and wait...and keep waiting and bam! Refreshed! But...that number is no longer what is going on...so...they look and ask...but can't you reduce that time? Sure I say, and show them the time refresh ranges. But even tho they see that were not 15 seconds for a refresh... Was a lot more. After that they tell ok...we will continue with CCPulse... I tell them that we can use it for wallboards were they don't require such speed. But they refuse because discrepancy on shown data is huge and would bring a problem of real understanding situations on their platform. A tool that is inaccurate is just unacceptable on a CC and is what Pulse is right now.

[Dionysis]

Have you tried RabbitMQ to shorten refresh times?  Apparently that's what's needed for that issue.  But who knows if you can deploy that according to the documentation, I just managed to get my Pulse with multiple collectors working, all you need to do is ignore the documentation and deploy the way you think it probably should be.

[cavagnaro]

Yeah, but still is not the same as Ccpulse.
The simple fact that you have to write down the stats name is something like 15 years ago...still need maturity on my opinion