Hi @Sara Kirankumar,
Pulse get data in this way:
1) Interactions -> 2) Media Server (SipServer/InteractionServer) -> 3) StatServer -> 4) Pulse Collector -> 5) Pulse
You define basic metrics on StatServer. Pulse Collector connect to StartServer and according to the configured dashboards and wallboards register the desired metrics and start to collect data, and generate data snapshots for Pulse. Pulse get data snapshots to feed your dashboards and wallboards.
Pulse solution is almost real time, it is quite intensive about consuming hardware resources. If you notice that Pulse is not "refreshing" on time, you should check:
- Check that your dashboard and wallboards are under control, it means: avoid to keep unused dashboards and wallboards
- Depending in your deploy, we notice Pulse collector could not refresh or generate new snapshots, it cause to Pulse to display same data without change.
- Check there is no problem in conectivity between components.
- Also check users conectivity between their workstation and Pulse, slow connections sometimes traduce in slow refresh on users views.
- Also check with your Genesys Partner your architecture, as I mention before, Pulse is quite demanding on resources but also as a web service it could reaching a limit on simoultaneous users. Perhaps, you have too many users against Pulse so you need add more Pulse instances.
I hope, it give you more clarity about Pulse
Regards,
SG
------------------------------
Saugort Dario Garcia
Interacciones Inteligentes S.A.
------------------------------
Original Message:
Sent: 09-24-2024 23:35
From: Sara Kirankumar
Subject: pulse
How data will be interchanged from the stat server to pulse, how pulse/cupules get auto-update with live stats, please explain in detail.
#Reporting/Analytics