Template to monitor Synology HA Solution
Template is based on Synology MIB Guide and monitor only an Synology HA Cluster
Is based on snmp v2 data from section Synology SHA MIB
Installation notes
Don’t forget to set the right community name in template Macros section
Before add to host set/add in Zabbix-> Administration -> General -> Value mapping
Synology Cluster Status
0 ⇒ normal
1 ⇒ warning
2 ⇒ critical
3 ⇒ upgrading
4 ⇒ processing
0 ⇒ normal
1 ⇒ abnormal
2 ⇒ disconnected
3 ⇒ empty
1 ⇒ True
2 ⇒ False
Items are explained in details
Triggers are explained and contain tags to show the problem details depending on received value
Created and tested with:
Synology DSM 6.2-24922on following models:
Zabbix version 4.0.0
You can write questions also to tudorticau@mail.ru
Nice to read when will deploy Synology HA environment this Synology HA White Paper
Tudor Ticau
Name | Description | Default | Type |
---|---|---|---|
{$SNMP_COMMUNITY} | <p>-</p> | public |
Text macro |
There are no template links in this template.
There are no discovery rules in this template.
Name | Description | Type | Key and additional info |
---|---|---|---|
Heartbeat Transfer Speed | <p>Transfer speed of heartbeat in kilo-byte-per-second</p> | SNMP agent |
heartbeatTxRate<p>Update: 60</p> |
Active Server Name | <p>Hostname of active server/NAS</p> | SNMP agent |
activeNodeName<p>Update: 60</p> |
Cluster Name | <p>Hostname of High-Availability cluster</p> | SNMP agent |
clusterName<p>Update: 60</p> |
Cluster Status | <p>Status of High-Availability cluster Possible values: normal (0) - The High-Availability cluster is healthy warning (1) - The High-Availability cluster has something went wrong. Action should be taken to resume High-Availability feature. Please refer to High-Availability Manager for more details. critical (2) - The High-Availability cluster is in danger, and should be resolved as soon as possible.Please refer to High-Availability Manager for more details. upgrading (3) - The High-Availability cluster is upgrading. processing (4) - The High-Availability cluster is undergoing some operation.</p> | SNMP agent |
clusterStatus<p>Update: 60</p> |
Cluster AutoFailover | <p>Whether cluster can failover once something went wrong true (1) false (2)</p> | SNMP agent |
clusterAutoFailover<p>Update: 60</p> |
Heartbeat Status | <p>Status of heartbeat connection Possible values: normal (0) - The heartbeat connection is normal abnormal (1) - Some information about heartbeat is not available disconnected (2) - The High-Availability cluster loses connection to passive server through heartbeat interface, or it is currently in split-brain mode empty (3) - The High-Availability cluster has no passive server.</p> | SNMP agent |
heartbeatStatus<p>Update: 60</p> |
Passive Server Name | <p>Hostname of passive server</p> | SNMP agent |
passiveNodeName<p>Update: 60</p> |
Heartbeat Latency | <p>Heartbeat latency in microseconds (10^-6 seconds)</p> | SNMP agent |
heartbeatLatency<p>Update: 60</p> |
There are no triggers in this template.
Template to monitor Synology HA Solution
Template is based on Synology MIB Guide and monitor only an Synology HA Cluster
Is based on snmp v2 data from section Synology SHA MIB
Installation notes
Don’t forget to set the right community name in template Macros section
Before add to host set/add in Zabbix-> Administration -> General -> Value mapping
Synology Cluster Status
0 ⇒ normal
1 ⇒ warning
2 ⇒ critical
3 ⇒ upgrading
4 ⇒ processing
0 ⇒ normal
1 ⇒ abnormal
2 ⇒ disconnected
3 ⇒ empty
1 ⇒ True
2 ⇒ False
Items are explained in details
Triggers are explained and contain tags to show the problem details depending on received value
Created and tested with:
Synology DSM 6.2-24922on following models:
Zabbix version 4.0.0
You can write questions also to tudorticau@mail.ru
Nice to read when will deploy Synology HA environment this Synology HA White Paper
Tudor Ticau
Name | Description | Default | Type |
---|---|---|---|
{$SNMP_COMMUNITY} | <p>-</p> | public |
Text macro |
There are no template links in this template.
There are no discovery rules in this template.
Name | Description | Type | Key and additional info |
---|---|---|---|
Heartbeat Latency | <p>Heartbeat latency in microseconds (10^-6 seconds)</p> | SNMP agent |
heartbeatLatency<p>Update: 60</p> |
Heartbeat Transfer Speed | <p>Transfer speed of heartbeat in kilo-byte-per-second</p> | SNMP agent |
heartbeatTxRate<p>Update: 60</p> |
Cluster Status | <p>Status of High-Availability cluster Possible values: normal (0) - The High-Availability cluster is healthy warning (1) - The High-Availability cluster has something went wrong. Action should be taken to resume High-Availability feature. Please refer to High-Availability Manager for more details. critical (2) - The High-Availability cluster is in danger, and should be resolved as soon as possible.Please refer to High-Availability Manager for more details. upgrading (3) - The High-Availability cluster is upgrading. processing (4) - The High-Availability cluster is undergoing some operation.</p> | SNMP agent |
clusterStatus<p>Update: 60</p> |
Cluster AutoFailover | <p>Whether cluster can failover once something went wrong true (1) false (2)</p> | SNMP agent |
clusterAutoFailover<p>Update: 60</p> |
Passive Server Name | <p>Hostname of passive server</p> | SNMP agent |
passiveNodeName<p>Update: 60</p> |
Heartbeat Status | <p>Status of heartbeat connection Possible values: normal (0) - The heartbeat connection is normal abnormal (1) - Some information about heartbeat is not available disconnected (2) - The High-Availability cluster loses connection to passive server through heartbeat interface, or it is currently in split-brain mode empty (3) - The High-Availability cluster has no passive server.</p> | SNMP agent |
heartbeatStatus<p>Update: 60</p> |
Active Server Name | <p>Hostname of active server/NAS</p> | SNMP agent |
activeNodeName<p>Update: 60</p> |
Cluster Name | <p>Hostname of High-Availability cluster</p> | SNMP agent |
clusterName<p>Update: 60</p> |
There are no triggers in this template.
Template to monitor Synology HA Solution
Template is based on Synology MIB Guide and monitor only an Synology HA Cluster
Is based on snmp v2 data from section Synology SHA MIB
Installation notes
Don’t forget to set the right community name in template Macros section
Before add to host set/add in Zabbix-> Administration -> General -> Value mapping
Synology Cluster Status
0 ⇒ normal
1 ⇒ warning
2 ⇒ critical
3 ⇒ upgrading
4 ⇒ processing
0 ⇒ normal
1 ⇒ abnormal
2 ⇒ disconnected
3 ⇒ empty
1 ⇒ True
2 ⇒ False
Items are explained in details
Triggers are explained and contain tags to show the problem details depending on received value
Created and tested with:
Synology DSM 6.2-24922on following models:
Zabbix version 4.0.0
You can write questions also to tudorticau@mail.ru
Nice to read when will deploy Synology HA environment this Synology HA White Paper
Tudor Ticau
Name | Description | Default | Type |
---|---|---|---|
{$SNMP_COMMUNITY} | <p>-</p> | public |
Text macro |
There are no template links in this template.
There are no discovery rules in this template.
Name | Description | Type | Key and additional info |
---|---|---|---|
Heartbeat Latency | <p>Heartbeat latency in microseconds (10^-6 seconds)</p> | SNMP agent |
heartbeatLatency<p>Update: 60</p> |
Heartbeat Transfer Speed | <p>Transfer speed of heartbeat in kilo-byte-per-second</p> | SNMP agent |
heartbeatTxRate<p>Update: 60</p> |
Cluster Status | <p>Status of High-Availability cluster Possible values: normal (0) - The High-Availability cluster is healthy warning (1) - The High-Availability cluster has something went wrong. Action should be taken to resume High-Availability feature. Please refer to High-Availability Manager for more details. critical (2) - The High-Availability cluster is in danger, and should be resolved as soon as possible.Please refer to High-Availability Manager for more details. upgrading (3) - The High-Availability cluster is upgrading. processing (4) - The High-Availability cluster is undergoing some operation.</p> | SNMP agent |
clusterStatus<p>Update: 60</p> |
Cluster AutoFailover | <p>Whether cluster can failover once something went wrong true (1) false (2)</p> | SNMP agent |
clusterAutoFailover<p>Update: 60</p> |
Passive Server Name | <p>Hostname of passive server</p> | SNMP agent |
passiveNodeName<p>Update: 60</p> |
Heartbeat Status | <p>Status of heartbeat connection Possible values: normal (0) - The heartbeat connection is normal abnormal (1) - Some information about heartbeat is not available disconnected (2) - The High-Availability cluster loses connection to passive server through heartbeat interface, or it is currently in split-brain mode empty (3) - The High-Availability cluster has no passive server.</p> | SNMP agent |
heartbeatStatus<p>Update: 60</p> |
Active Server Name | <p>Hostname of active server/NAS</p> | SNMP agent |
activeNodeName<p>Update: 60</p> |
Cluster Name | <p>Hostname of High-Availability cluster</p> | SNMP agent |
clusterName<p>Update: 60</p> |
There are no triggers in this template.