Health Check

Genesys Pulse Web Service API provides ability for the health check through /api/plugins/wbrt/health/detail.

The following

• snapshotWritingStatus—Snapshots are written to a file system, snapshot generation and writing process itself do not depend on present/missing connections. If connection to Stat Server missing, data may be all N/A, but still snapshots are generated and written.
• pendingLayoutStatusChangesCount—This is a summary number of pending layouts to activate, deactivate, or recheck. This process depends on availability of the connection to DB Server. If the connection is present, this number changes, as layout activation/deactivation/recheck are processed. Stalled nonzero number may indicate missing connection to DB Server. Genesys Pulse Collector needs to read changed layouts and new layout definitions, which requires active connection to DB Server.
• maxStatisticValueDelay—This value depends on the number of layouts, their refresh period, performance of CPU, sufficient memory availability (no swap operations caused by Genesys Pulse Collector), performance of the file system. There is no recommended value; however, most layouts typically have the same refresh interval, if this number Olena's question: "this number" means the number that the maxStatisticValueDelayis is set to, correct? Can I use "the setting of the maxStatisticValueDelay" instead? is higher than some part of this interval (say 25-50%), then you want to consider increasing resources. Values do not indicate that something is totally wrong, but may indicate that Genesys Pulse Collector can perform better if it runs with more elevated settings (more processing threads) and faster drives/file systems for the snapshots storage.

Olena's comment: https://jira.genesys.com/browse/WBRT-14530 and https://jira.genesys.com/browse/WBRT-14422