We regroup on this page the main KPI to follow the Calypso activity.

Calypso clients

HPA Home page

This tile displays the number of connected clients to the dataserver.

  • current value : the numbers of connected clients at the end of the selected period (most up-to-date value)
  • max value : the maximum number of clients connected during the period

The source values are the same as dataserver tab.

Engine status

HPA Home page

This tile displays the running engines and the total number of engines.

Clicking on the icon open a popup with the detailed engines list.

HPA Home page

You can filter, export and sort the list of engines.

Calculator grid

HPA Home page

This tile displays the percentage of running calculator in the grid.

  • current value : the numbers of calculator running at the end of the selected period (most up-to-date value)
  • max value : the maximum number of calculator running at the same time during the period

The source values are the same as riskserver tab.

Events

Calypso exchange a lot of events between its different components :

  • JMS Messages (underlying technical part of the PS Events) managed by the event server
  • PS Events, the function part of the message and a Calypso layer in top of JMS Message
  • Pending events / Unconsummed Events : the engines read immediatly JMS Message/PSEvents from event server and store them into their own queue

Events server

HPA Home page

The heart of the event system exchange, all components should consume the messages published on the differents queues and topic. All the queue should be at zero : instant event consumption by client.

PS Events

HPA Home page

In this tile, the number of psevents sent by dataserver is displayed (the details of psevents is in the dataserver tab). The sum of events consumed by all clients is also displayed, there is no details for now of the sum of events per clients.

Pending Events

HPA Home page

In this tile, the number of psevents sent by dataserver is displayed (the details of psevents is in the dataserver tab). The sum of events consumed by all clients is also displayed, there is no details for now of the sum of events per clients.

If the value “-1” is displayed then check dataserver logs, it means that database returns an error, this value is directly read from Calypso API.

Stalled requests

HPA Home page

A stall request is a request than running during more than 30 seconds.

This tile display the number of stalled requests during the selected period. You can have details on the requests by clicking on the icons.

HPA Home page

The detailed dialog show the host, the component and the method where long response time has been detected. There is no relationship between methods in this dialog, but it’s often the case that a long request on dataserver can be link to a client side request or the generic dataserver frontend (Frontends|Apps|dataserver) or the generic backend dataserver (Backends|Remote|dataserver).

Objects count

HPA Home page

This graph shows the number of modified objects (i.e objects saved in database) in the dataserver :

  • Trade
  • message
  • CRE
  • transfer

Objects not inserted/updated in Database

Just under the graph, an expansion panel with title “Elements with no activity on this period…” displays the list of Objects that have not been inserted/updated in Database during the monitored period.