Call-home / Alerting: Difference between revisions
| Line 16: | Line 16: | ||
== External Monitoring == | == External Monitoring == | ||
Besides access via REST APIs and the scriptable QS CLI, QuantaStor supports traditional protocols like SNMP and cloud services like [https://wiki.osnexus.com/index.php?title=Librato_Metrics_Integration Librato Metrics] and [https://wiki.osnexus.com/index.php?title=Idera_Uptime_Cloud_Monitor_Integration]. | Besides access via REST APIs and the scriptable QS CLI, QuantaStor supports traditional protocols like SNMP and cloud services like [https://wiki.osnexus.com/index.php?title=Librato_Metrics_Integration Librato Metrics] and [https://wiki.osnexus.com/index.php?title=Idera_Uptime_Cloud_Monitor_Integration Idera Uptime Cloud Monitor Integration]. | ||
== Generating Alerts == | == Generating Alerts == | ||
QuantaStor systems report alerts at various severity levels like ''ERROR'' and ''WARNING''. For example, when a disk or battery needs to be replaced it will produce ''WARNING'' and some ''ERROR'' level events from the controller which in turn generate alerts. Alerts are sent via all configured mechanisms so a system with email and PagerDuty configured will see events send to administrators both via email and PagerDuty mechanisms. To generate a test alert one may use the '''qs alert-raise''' QS CLI command or use the '''Generate Test Alert''' button in the QuantaStor web management interface. | QuantaStor systems report alerts at various severity levels like ''ERROR'' and ''WARNING''. For example, when a disk or battery needs to be replaced it will produce ''WARNING'' and some ''ERROR'' level events from the controller which in turn generate alerts. Alerts are sent via all configured mechanisms so a system with email and PagerDuty configured will see events send to administrators both via email and PagerDuty mechanisms. To generate a test alert one may use the '''qs alert-raise''' QS CLI command or use the '''Generate Test Alert''' button in the QuantaStor web management interface. | ||
Revision as of 19:56, 7 February 2020
QuantaStor has a number of mechanisms for call-home alerting when systems report hardware or software issues. They include standard mechanisms like email and SNMP but also include various cloud based call-home mechanisms which are "web-hook" based.
- SNMP
- PagerDuty
- Slack
- Mattermost
- User supplied custom script (/var/opt/osnexus/alerthandlers)
The Alert Manager also allows one to specify thresholds for low storage pool capacity remaining. Administrators should take action to expand the available capacity or migrate resources to ensure continuous normal operation of systems whenever a pool reaches 80% full as performance can degrade and an out-of-space condition can lead to downtime for users. For more information on the configuration of PagerDuty and other monitoring mechanisms see the Monitoring and Cloud Metrics Integration guide here.
Navigation: Storage Management --> Storage System --> Storage System --> Alert Manager (toolbar)
The Alert Manager documentation has moved to Alert Manager / Call-home Alerting.
External Monitoring
Besides access via REST APIs and the scriptable QS CLI, QuantaStor supports traditional protocols like SNMP and cloud services like Librato Metrics and Idera Uptime Cloud Monitor Integration.
Generating Alerts
QuantaStor systems report alerts at various severity levels like ERROR and WARNING. For example, when a disk or battery needs to be replaced it will produce WARNING and some ERROR level events from the controller which in turn generate alerts. Alerts are sent via all configured mechanisms so a system with email and PagerDuty configured will see events send to administrators both via email and PagerDuty mechanisms. To generate a test alert one may use the qs alert-raise QS CLI command or use the Generate Test Alert button in the QuantaStor web management interface.