Alarm function is offered as a separate service within CoreStack™. You can create their own alarms based on certain conditions. When such alarm condition is met, a specific action can be triggered. The triggered action can be the execution of a Template or Script.
The trigger for the alarm can be from anywhere including a Monitoring Tool such as Nagios, or from any other external services as well. The alarm can be manually executed right from the UI as well.
Before an alarm is created in the system, it is essential to have the required Template or Script available in the system. If the Template / Script is available in your local system or in a public URL, it must first be uploaded into CoreStack™. Refer the Create Template or Create Script sections for more information about creating a custom Template / Script.
Select any alarm to view its details in the right panel.
Other actions available:
- Edit or Delete the Alarm using the action icons available at the top of the right panel.
- To “Execute” an alarm manually, click the play icon in the Action column. You will see a confirmation message and once you confirm, the Template / Script mapped to this Alarm will get executed.
- Choose the Alarm function from the Menu and then click Create at the top right corner.
- You will see a pop-up as shown below
- Following details are to be entered.
- Provide a Name for the alarm – This is for your own reference.
- Select the type of alarm.
- Select the action – either Execute Template (or) Execute Script. Based on the selected action, Template List or Script List will be displayed.
- From the list, select the Template or Script that must be executed when the alarm condition is met.
- Click on “Next” button to proceed to the next tab
- In the next tab, you need to provide the input values to execute the Template or Script.
- Select the Cloud Service Account against which the template must be executed.
- Select the Resourcegroup, Locations as applicable
- Choose the Nagios Service Account to associate with this template
- Enter the Instance Name and IP Address
- Click Create
- Alarms created will be listed in the data table. You can verify if the recently created alarms are listed here. To execute an alarm from the UI, click the execute icon.
To set-up auto remediation, you need to configure this alarm to be triggered by an external event. Let us take an example of configuring the above alarm to be triggered automatically based on a monitoring event from Zabbix tool.
There is a marketplace template called “Alarm_Configuration_Zabbix”
Execute this template. You will see the pop-up as below:
Host_ID: You can get this from the Resource List of Zabbix from Integrated Tools page. Or if you have access to the Zabbix dashboard, you can retrieve it from the Configurations -> Hosts page.
- Alarm: Select the preferred alarm from the drop-down. In this example it is our “Test_Alarm”
- TriggerID: This is again available from the “Resource List” within CoreStack™ or you can also get it from Zabbix. In Zabbix, it is available in the path: Configuration > Hosts > Trigger
- Action Name: This is for your own identification when the template execution. So you can provide any name.
Upon execution of this template:
- Zabbix will be configured to auto-remediate and trigger the CoreStack™ Alarm which executes the template
- To test this – stop the AWS Instance specified in the alarm . Immediately, Zabbix triggers a down alert and it triggers the alarm which in turn executes the template to restart the VM.
- The VM will run again within minutes, with no manual intervention.
You can execute much complex remediation scenarios with CoreStack™ since you have the ability to execute Templates or Scripts that can perform wide range of actions.