A number of things can happen that causes your GB instance to lose connectivity to Exchange and/or internet:
Exchange updates
Time sync
IP change on IP restricted APIs
Server / VM crash
If this happens, the only way a user can find out is by directly monitoring the PC / server / VPS and check that GB is still cycling. This may not be possible in certain situations (away from desk, on holiday, forget to check). A prolonged disconnection can be very bad, particularly for futures trading.
Solution
Since people take phones everywhere, a simple pinging routine built within GB Telegram bot would be very useful. For example, you can configure GB to send a periodic "hello" message to TG every x mins (configurable in config.js). The contents of which can be:
**GB OK**Connection to exchange OK
If this hello message is not being recieved every x mins, the user knows there is a problem with the instance. Additionally, if the user recieves the following message, they know there's an API / Exchange issue:
Great idea for an error alert... not so much for the "GB OK", as getting a ding every five minuets will get old quickly.
Not sure you'll get a response here tho, I've submitted an issue and have heard nothing.
Problem
A number of things can happen that causes your GB instance to lose connectivity to Exchange and/or internet:
If this happens, the only way a user can find out is by directly monitoring the PC / server / VPS and check that GB is still cycling. This may not be possible in certain situations (away from desk, on holiday, forget to check). A prolonged disconnection can be very bad, particularly for futures trading.
Solution
Since people take phones everywhere, a simple pinging routine built within GB Telegram bot would be very useful. For example, you can configure GB to send a periodic "hello" message to TG every x mins (configurable in config.js). The contents of which can be:
**GB OK**
Connection to exchange OK
If this hello message is not being recieved every x mins, the user knows there is a problem with the instance. Additionally, if the user recieves the following message, they know there's an API / Exchange issue:
**GB Error**
Connection to exchange fault!!