Monitoring Trading Signal Properties with MySQL and MQL5

Summary

The article presents an MQL5 service that periodically reads the properties of trading signals available in the terminal, compares each snapshot with previously stored values, and writes updated records to MySQL when it detects changes. It organizes properties by data type, uses the signal identifier to match records, and derives a database table name from the broker server and account login. Reading the latest stored snapshot lets the service continue change detection after a restart.

A companion Expert Advisor displays the history of a selected property and supports filtering signals through database queries. The implementation discusses combining queries and keeping a persistent connection alive during frequent requests, with a ping to detect or prevent connection loss. The article is an engineering example for tracking provider characteristics such as leverage, rating, and subscriber count; it does not assess whether those changes predict trading performance. It notes that signal-property refresh timing depends on terminal behavior and describes the observed update schedule for the version discussed.

Key ideas

• Poll signal properties, compare snapshots, and store changed records in a MySQL database.
• Group signal attributes by data type so each property can be read and stored appropriately.
• Use the latest database snapshot to restore comparison state after the service restarts.
• Display property histories and filter signals with database queries.
• Keep frequent-query connections alive and monitor them with a ping.

Tags

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.