Filters Area

Filters Area

LISA Filters Area Overview

LISA Filters Area Overview

LISA Server Connection

In the Filters area, on the top left there is the logo of LISA Clearing Engine and a bar representing the status of the connection between LISA Front End and the LISA Server.

Red bars, the LISA Front End cannot connect to the LISA Server. This is either because of a network error or LISA server is down.

Moving green bar, the LISA Front End is connecting to the LISA Server.

Green bars, it means that the connection to the LISA Server has been established successfully.

Yellow moving bars, the LISA Front End is having longer than normal delays getting updates from the LISA server. Hovering over this field will provide a popup showing the current delay in number of unprocessed messages.

Note It is important for the LISA Front End to connect to the LISA Server, otherwise there will not be any real-time feeds and you will need to constantly refresh the Front End.

LISA Module Status

Next to the LISA server connectivity status is the Who is alive icon or the LISA Performance Monitor . These features allow you to check the status of different LISA processes. This functionality has been implemented to keep the user informed of the state of the different LISA modules and provide details of the versions.

Who is Alive Form

If all the LISA components are up and running, the small screens will be green .

If one or more of them isn't up and running, the small screens will be flickering from red to green.

The following table explains different sections and columns on the Who Is Alive Form.

Field Default Comment
Request Interval 60 In seconds, the environment will send out a heartbeat request to gather performance stats in the environment.
Send Request Now This will initiate an immediate request for data from the LISA environment for the latest performance stats. Next to this button is a Last Request at value that shows the last time the heartbeat request was received.

Quick Search This allows for a user to enter a value into the text box and click the magnify glass icon to quickly filter the grid values. Pressing the large X will clear the filtered grid and show all items.
Radio Buttons All

The radio button filter based on the Type column so the corresponding value like Gateway will filter all exchange and generic gateways in the LISA Environment.

All: Will display all items in the environment

Down: Will display all modules that are not responding to heartbeat requests implying there is either a network issue or the module is not running.

Gateway: Displays all Exchange and Generic Gateways.

Server: Simply displays the LISA Server module.

Matching Engine: Will display only the Matching Engine types.

Input Transfer: Will show the Order and Trade Input modules.

Import: Will show all import types like LISA File Import.

Export: Will show all export types like Teo Export LISA or LISA GMI Export.

Note The module type is driven of the user login defined for the module under the menu [Configuration]>[Security]>[Login] under the system logins you can edit the type under the General tab of the system user.
Grid Section
Type Column
Status Column

No connection established with the LISA server, or Exchange Gateway is not responding to heartbeats from Generic Gateway.

Connection active with the LISA server.

Status of Exchange Gateway is unknown because corresponding generic gateway is down.

Version The Binary Version option.
Login

The LISA system user used for this module. Please note that the LISA Gateway Exchange and the Generic Gateway use the same login, except that the login for the exchange will have the following tail /Exchange.

Examples:

GTW_EUREX = LISA Gateway Generic for Eurex

GTW_EUEX/Exchange = LISA Gateway Eurex Fixml
Computer Provides the Hostname where this module is running.
IP Provides the IP Address for where this module is running.
Last Ping The time the module last provided a heartbeat response.
Score The score provides the average number of lines or messages the module is currently able to process. Depending on the module, different scores will be calculated. For a generic gateway module it will only provide the number of lines the module is able to insert per second on average. In this example, the LISA 40.5 LSI lines/s mean the LISA generic gateway is currently able to insert on average 40.5 trade lines into LISA per second. If this is an Exchange module (/Exchange), then the score will provide an IN and OUT value. In the image below we see in the second line IN:265.8msg/s which is to say the LISA gateway Exchange is able to read 265.8 messages per second from the exchange feed and it is sending out 14.2 messages per second to the exchange for clearing.

Usage The usage column operates in a similar fashion to Score. Here it calculates a percentage for the module based on the score calculated and the maximum score it has performed though out the day. It is reset on the environment restart. In the below image we see the results of LISA Gateway Exchange (/Exchange) currently reaching 4% of the maximum threshold experience topday.

Core Response Time The core response time is only provided by modules that connect directly to the LISA server. This is the time it is taking for the module to send a message to the LISA Server.

Exchange Response Time This is based on the time the module takes to provide a response to each clearing request.

Estimate Delay Estimated Delay is calculated base on the score and the number of messages on the exchange feed that still need to be processed for exchange gateways (/Exchange). On the generic gateways this time is based on the time its taking to insert records into LISA and the number of lines still leI to process.

LISA Performance Monitor

The screen allows for a quick overview on the module’s performance in the LISA environment. The results are broken down into the following sections:

  • Trade/s: The number of Trade events the module has processed since the last refresh per second averaged.
  • Orders/s: The number of order events the module has processed since the last refresh per second averaged.
  • Clear Requests/s: The number of clearing request the module has received/send since the last refresh per second averaged.
  • Clear Responses/s: the number of clearing responses from the exchange the module has received/sent since last refresh per second averaged.
  • Events/s to all LISA: The number of message events the LISA server has sent to all LISA front ends.
  • Events/s to all Modules: The number of message events the LISA server has sent to all LISA modules like LISA Gateway Generics. Events/s: The number of events the module is sending/receiving since the last refresh per second averaged.
  • Matching/s: The number of matching events the module has done since last refresh per second averaged.

    • You will also noOce a purple S or blue R which simply denotes Sending and Receiving, respectively.

    Quick Filter Bar

    Allows for the filtering of the Order and trade grid based on a number of fields with in that grid. As you filter the grid will filter, to clear the filter click the red X which clears the filter.

    Execution time: search for a matching value e.g. for exec time in FTE: "2020/12/16 15:01:03.000" or 15:01

    Env (used on LME for the ring Ome code): e.g. R1

    Dealing with a lot of information in the LISA Front End allows for the drill down to the information seamlessly. That's the reason why the LISA Front end offers different types of filters:

    Next:

    LISA Predefined Filters