Every connection gets a health card: CPU, memory, disk, queries per second and a 48-hour trend. A database login cannot see its machine, so Migratrix can read the host's own figures from the monitoring you already run: Prometheus, Zabbix or Datadog, or CloudWatch, Azure Monitor and Google Cloud Monitoring for managed databases.
Queries per second, sessions and cluster instances always come from the database. A metrics source fills in what the login cannot see; a figure it does not have stays the database's own.
| Engine | From the login alone | With a metrics source |
|---|---|---|
| PostgreSQL | No CPU, memory or disk figure. The card shows active sessions. | Host CPU, memory, disk, disk IOPS and network. |
| MySQL, MariaDB, TiDB | No CPU. Memory is the InnoDB buffer pool, disk the tablespace files. | Host CPU, memory and disk in their place. |
| Oracle | Host CPU per instance, including RAC. Memory is SGA and PGA, disk the data files or ASM disk groups. | The machine's memory and file systems. |
| SQL Server | CPU, host memory and the volumes that hold database files. | The whole machine's figures, and network. |
node_exporter; your own PromQL replaces them when your exporters or labels differ.The Executor next to your databases queries the monitoring system. Its address only has to be reachable from there, and its password, token or AWS key is kept encrypted on the Executor host with your database credentials.
Each kind is a package on the Executor, verified, and signature-checked where you require it, by the same rules as an engine plugin. A package brings its own form, and the cloud SDKs live only in the packages that need them, not in the Executor itself.
Nothing is installed in your databases or written to your monitoring. Adding, changing or deleting a source is recorded in the audit ledger, with which secret changed and never its value.
| In the product | Not claimed |
|---|---|
| A health card per connection, sampled about once a minute, with a 48-hour hourly trend and filters by environment and health. | A monitoring product. Keep your dashboards and on-call alerting; this is the view next to the change you are about to run. |
| Host figures from Prometheus-compatible APIs (including the managed services of AWS, Azure and Google Cloud), Zabbix, Datadog, CloudWatch, Azure Monitor and Google Cloud Monitoring. | AlloyDB, Azure SQL elastic pools, New Relic or Dynatrace as sources. |
| One set of thresholds for the health label: 75% for Warning, 90% for Critical. | Threshold notifications by email or Slack, or thresholds per server. |