replication-manager embeds a graphite database to store metrics about databases and proxies status.
replication-manager 2.1 expose Prometheus metrics for all servers under clusters
No extra ports required (since v3.1.1): The embedded Graphite render API is proxied through the replication-manager HTTPS API. External tools and dashboards can query metrics directly over the existing HTTPS connection — there is no need to expose any of the Graphite carbon ports (
graphite-carbon-api-port,graphite-carbon-server-port, etc.) to the network.The render endpoint follows the standard Graphite render API:
GET /graphite/render?format=raw&target={graphite-target}&from={unix-timestamp}&until={unix-timestamp}Example — fetch the InnoDB transaction lock latch wait across all servers:
https://repman-host/graphite/render?format=raw&target=alias(sumSeries(mysql.*.mysql_global_status_wait_synch_rwlock_innodb_trx_rseg_latch),'')&from=1776757548&until=1776764748This is the same endpoint used internally by the workload and log plugins to load their rolling metric history for spike detection.
graphite-embedded (1.1)| Item | Value |
|---|---|
| Description | Enable Graphite Server. |
| Type | Boolean |
| Default Value | false |
graphite-metrics (1.1)| Item | Value |
|---|---|
| Description | Collect and send metrics to a Graphite Server. |
| Type | Boolean |
| Default Value | false |
graphite-carbon-host (1.1)| Item | Value |
|---|---|
| Description | Host of the Graphite server to send metrics. |
| Type | String |
| Default Value | "127.0.0.1" |
graphite-carbon-port (1.1)| Item | Value |
|---|---|
| Description | TCP & UDP port of the Graphite server to send metrics. |
| Type | Integer |
| Default Value | 2003 |
graphite-carbon-api-port (1.1)| Item | Value |
|---|---|
| Description | Graphite Carbon API port. |
| Type | Integer |
| Default Value | 10002 |
graphite-carbon-link-port (1.1)| Item | Value |
|---|---|
| Description | Graphite Carbon Link port. |
| Type | Integer |
| Default Value | 7002 |
graphite-carbon-pickle-port (1.1)| Item | Value |
|---|---|
| Description | Graphite Carbon Pickle port. |
| Type | Integer |
| Default Value | 2004 |
graphite-carbon-pprof-port (1.1)| Item | Value |
|---|---|
| Description | Graphite Carbon pprof port. |
| Type | Integer |
| Default Value | 7007 |
graphite-carbon-server-port (1.1)| Item | Value |
|---|---|
| Description | Graphite Carbon HTTP port. |
| Type | Integer |
| Default Value | 10003 |
HTTP Graph are display via the giraffe JS library.
Customizing the trends can be done modifying.
/usr/share/replication-manager/dashboard/static/graph.js
Set the replication-manager host or IP address to tell where to found the graphite server
Replication and some databases status metrics are pushed inside carbon, the metrics are pushed with the server-id prefix name. to get unicity against nodes

We can advise usage of Statd and Collectd on each database node and send metrics to replication-manager whisper port to add extra system metrics to the cluster.
One can create custom dashboard via Grafana.
The port to use as direct data source in grafana is drive by graphite-carbon-api-port default 10002.
http://127.0.0.1:10002/

In replication-manager 2.0 more metrics are pushed to graphite using prefix
Some Grafana dashboard using such metric names can be found in the share directory of replication-manager.
http://demo.signal18.io/api/prometheus