Skip to content

Latest commit

 

History

History
122 lines (98 loc) · 2.57 KB

alert.md

File metadata and controls

122 lines (98 loc) · 2.57 KB

Alerting

replication-manager offer multiple way of alerting on server status change

External script

An alert script can be trigger if enable via this config file parameter

alert-script = "path-to-script"

The following arguments are passed to the script

  • Server URL
  • Server previous state
  • Server current state

Email

An email can be send via postfix using the following parameters

  • Alert email sender, a valid postfix user should be used
mail-from = "user@hostname"
  • Alert email SMTP server in host:[port] format
mail-smtp-addr  = "localhost:25"
  • Unique email to send the alert
--mail-to = "alert@signal18.io"

Important Note No secure mail server is supported .

External status monitoring

The API provide some useful endpoint to check for status

Checking for monitoring daemon status can be done via URL
http://replicaion-manager-host:3000/api/status

 {"alive": "running"}
 {"alive": "starting"}

http://replicaion-manager-host:3000/api/clusters/{clusterName}/status

{"alive": "running"}
{"alive": "errors"}

http://replicaion-manager-host:3000/api/clusters/{clusterName}/topology/alerts

Client call checking status

replication-manager-cli status

running

replication-manager-cli status --cluster=cluster_haproxy_masterslave

errors

replication-manager-cli status --cluster=cluster_haproxy_masterslave --with-errors

{
	"errors": [
		{
			"number": "ERR00021",
			"desc": "All cluster db servers down",
			"from": "TOPO"
		},
		{
			"number": "ERR00010",
			"desc": "Could not find a slave in topology",
			"from": "TOPO"
		},
		{
			"number": "ERR00012",
			"desc": "Could not find a master in topology",
			"from": "TOPO"
		}
	],
	"warnings": [
		{
			"number": "INF00001",
			"desc": "Server 127.0.0.1:3310 is down",
			"from": "TOPO"
		}
	]
}

replication-manager-cli bootstrap --cluster=cluster_haproxy_masterslave

Can't found topology after bootstrap

The cluster is not provisioned launch it manually or via the replication-manager-tst or replication-manager-pro release

replication-manager-cli bootstrap --cluster=cluster_haproxy_masterslave --with-provisioning

Provisioning done

replication-manager-cli status --cluster=cluster_haproxy_masterslave

running

Alerting from logs

The logs can be send to syslog services via

log-syslog

One can look at log tag type=state to trigger some custom alerting We may improve log facilities to send them to various log analyze systems, contact signal18.io for NRE