Fail-Watch and Trading System Warnings: Difference between revisions
From MultiCharts
Fail-Watch and Trading System Warnings (view source)
Revision as of 15:58, 7 October 2020
, 7 October 2020no edit summary
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
The Fail-Watch alerts and trading system warnings were introduced in the frames of our new Fail-Watch system. | The Fail-Watch alerts and trading system warnings were introduced in the frames of our new Fail-Watch system. | ||
The platform generates an alert if the limits of the OS, hardware, bandwidth, software and/or broker processing speed is reached. | The platform generates an alert if the limits of the OS, hardware, bandwidth, software and/or broker processing speed is reached. | ||
== Trading | == Trading System Alerts == | ||
===Order status is processed longer than xxxx ms — TR01 === | ===Order status is processed longer than xxxx ms — TR01 === | ||
The status of the order is being processed in the Trading Server longer than xxxx ms. | The status of the order is being processed in the Trading Server longer than xxxx ms. | ||
Line 23: | Line 23: | ||
<br> | <br> | ||
== Fail-Watch | == Fail-Watch Alerts == | ||
In MultiCharts 14 we introduced the monitoring of the auto trading orders' speed from the moment of generation up to reaching the trading plugin. The monitoring is implemented by using test messages. | In MultiCharts 14 we introduced the monitoring of the auto trading orders' speed from the moment of generation up to reaching the trading plugin. The monitoring is implemented by using test messages. | ||
<br>The way that test messages perform is identical to the way that real orders follow in MultiCharts (from module to module). The only difference is that it is not sent to the broker plugin and to the broker itself. The test message is intended to determine the load on the info channels within the application and the performance of the system in general. If the test messages are delayed or failing it means that the load on the internal info channels is too high so it leads to the queue of orders and statuses where they are waiting to be sent and processed. | <br>The way that test messages perform is identical to the way that real orders follow in MultiCharts (from module to module). The only difference is that it is not sent to the broker plugin and to the broker itself. The test message is intended to determine the load on the info channels within the application and the performance of the system in general. If the test messages are delayed or failing it means that the load on the internal info channels is too high so it leads to the queue of orders and statuses where they are waiting to be sent and processed. |