+1 888 340 6572 GET STARTED
MultiCharts Project Management
Go to the previous open issue
Go to the previous issue (open or closed)
Please log in to bookmark issues
Open Feature request MC-826

Automating Error/Trading Notifications

Go to the next issue (open or closed)
Go to the next open issue

When using Auto-trading future, given that auto-trade algos can run 24/7 (in the case of
currency trading), it becomes critical to monitor ongoing status of the whole system for
any errors/warning etc which normally require immediate attention due possible system errors/broker connection failures/network connection failures etc.
1. Given that muliticharts typically does a pretty good job by recording those errors under logs
tab in Order and Position Tracker, it would be good if when errors were generated, it was possible to configure instant notifications with error details to be sent to user in the form of e-mail/sms message.
2. And also extend the above feature for the Algo generated trades, to be able to send e-mail/sms to user to notify what a trade has taken place. This helps to monitor for
potential unexpected execution behaviour due to issues with broker comms/etc.
Wish list:
The notifications to be sent should be configurable by Profile, Strategy, Instrument and Cantergory (the same as options are currently available under the logs tab in the order and position tracker.
Possible suggestions
For SMS notification probably the easiest way to implement this would be to create a text
file for each event matching profile/strategy/instrument and category filter requirement in the specific folder. Users then can then implement their custom scripts which will  check the folder in realtime (every 1 minute or so) for new files and if one is created in the folder when an event is generated it would use a custom script to send e-mail/sms to required destination and then delete text file from the folder. Text file would contain the same details/fields as under the logs tab of Order and Position Tracker.

Steps to reproduce this issue

N/A - New future request.

Comments (0)
Issue basics
  • Type of issue
    Feature request
  • Category
    Not determined
  • Targeted for
    Not determined
  • Status
    Under Review
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (3)
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
  • Severity
Attachments (0)
There is nothing attached to this issue
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates