Monitoring the health and performance of your appliance is a critical task. The checklist below lists the steps that you need to complete to ensure that your Beeks Analytics appliance is sufficiently monitored.
Step | Purpose | Section of this document | |
|---|---|---|---|
1 | Identify where alerts will be sent. | Choose where Beeks Analytics will route alerts to. This can be an Incident Management Platform that’s responsible for onbound routing, silencing, and general lifecycle of alerts/incidents, such as Opsgenie, Pager Duty, or Jira Service Desk. Alternatively, it can be a Slack channel, Teams channel, or mailing list. | |
2 | Configure external monitoring system to monitor iDRAC and OS endpoints. | Set up external monitoring to monitor iDRAC and OS endpoints to detect catastrophic Grafana or OS failures. Examples of suitable infrastructure monitoring systems: Geneos, Nagios, Zabbix, Datadog, Checkmk, LibreNMS. | |
3 | Configure your chosen alerts endpoint to receive alerts and monitor iDRAC and OS endpoints. | Once done, you’ll receive hardware and Grafana alerts. | |
4 | Choose the Beeks Analytics Health alerts you want to receive. | Beeks provides a | |
5 | Configure Grafana to send alerts to the contact points agreed in Step 1. | Instruct Grafana where to send notifications if an alert fires. | Setting up Contact Points and Notification Policies for pre-defined Alert Rules |
6 | Enable the Beeks Analytics Health alerts you want to receive. | By default, the alerts are disabled, so you’ll need to enable the alerts you are interested in. | Enabling/Disabling pre-defined Alert Rules by invoking vmxadmin |
7 | Begin monitoring the health of your Beeks Analytics appliance | Familiarise yourself with the VMX-Explorer Health dashboards and error codes for iDRAC etc. |