Manage Alarm Settings

Created by Lakshmi Vasanth, Modified on Tue, 19 Nov, 2024 at 3:33 AM by Jaseem Masood

You can create and manage general alarms related to CPU usage, memory usage, disk usage, system up/down, and Ceburu agent status.

Adding an Alarm

1. Navigate to Settings > Configurations > Alarms.

The Alarms page is displayed.

2. To add a new alarm, click Add New Alarm.

The Add New Alarm dialog is displayed.

Note: All the fields with an asterisk (*) are mandatory.

3. Enter/ select the required values in the respective fields. Refer to the table below for fields and their descriptions.

Field	Description
Alarm Name	Name of the alarm
Alarm Type	Type of the alarm. The available options are CPU Usage, Memory Usage, Disk Usage, System Up/Down, and Ceburu Agent Status.
Interval	Interval period of the alarm.
Frequency	Frequency at which the alarm can be repeated.
Threshold (%)	Minimum threshold percentage of the specified indicator (based on alarm type) that triggers the alarm.
User Group	Name of the user group to be notified when the alarm is triggered.
Device Group	Device group to which this alarm is intended for.
External User	Email address of any external user who needs to be notified about the alarm.
Status	Indicates whether or not this alarm is enabled.

4. Click Save.

The new alarm is created.

Adding an External User

You can add an external user’s email address to be notified whenever an alarm is triggered.

1. Click Add External User.

The Manage External Users dialog is displayed.

2. Enter the email address of the external user in the Email field.

3. Click Save.

The email address is added and this user email address can be selected while creating an alarm.

Ceburu Alarms Configuration:

No	Alarm Type	Interval by User	Frequency by User	Auto Acknowledge	Auto Close	Description
1	CPU Usage	Options for user 3 Minutes 5 Minutes 10 Minutes 15 Minutes 20 Minutes Selected 3 Minutes	Options for user 3 hours 6 hours 9 hours 15 hours 24 hours Selected 3 hours	User Selected Freq. 3 hours	5 Minutes	Once the CPU reaches the configured threshold, Ceburu checks for the consistency of the spike with the interval set by the customer. If the spike is consistent for more than the interval set (>= interval set), Ceburu will send the first alarm mail to all the users assigned in the group for that alarm. Let’s say the spike starts at 10.00am and remains above the threshold level till 10.03am, the first mail will be sent. We flag the first mail as ‘WARNING’ email. At this stage, we add a trigger in the trigger table, which will be listed in the trigger page and the state was ‘Problem’. Auto Acknowledge: If none of the users acknowledges the trigger, Ceburu waits for 3 hours(user selected frequency) and auto acknowledge the trigger and assign it to ‘auto-usergroup users’ of the company. For e.g. If the spike reaches the threshold at 06.00am, first email will be send at 06.03am. If none of the users acknowledge, Ceburu auto-acknowledge at 09.03 and send out the email. If CPU usage drops below the threshold, the system waits for 5 minutes. If usage remains below the threshold for that duration, the issue is marked as resolved, and the trigger state changes from 'Problem' to 'Resolved.' If the issue is fixed and ‘Closed’, Ceburu will close the trigger, and change the state from ‘Problem’ to ‘Resolved’ and send the email for ‘auto-usergroup users’. If the issue is not fixed, Ceburu sent the follow-up ‘Critical’ email at 09.03am the next day (after 24 hours). This will happen every day. This email also send to ‘auto-usergroup users’. Manual Acknowledge: User has to enter the hours user needs to fix the issue and click on the Acknowledged option. When the user changes the state to ‘Acknowledged’, Ceburu sends a mail to the user who acknowledge the trigger. Ceburu will not send follow-up emails to the users, till the agreed hours is reached. Once the issue is fixed, the acknowledged user or any one of the admins should come to this popup and change the trigger state to ‘Closed’ Ceburu sends a mail to the user who acknowledge the trigger. If the issue is not fixed within the agreed hours, Ceburu will send the follow-up email to the auto-user. From this point Ceburu will send follow up emails once in 24 hours to the auto-user Note: All above will happen ONLY if the Global Alarm setting is in ON state. OFF will not notify the users on any triggers, except if the Probe is down.
2	Memory Usage	Options for user 3 Minutes 5 Minutes 10 Minutes 15 Minutes 20 Minutes Selected 3 Minutes	Options for user 3 hours 6 hours 9 hours 15 hours 24 hours Selected 3 hours	User Selected Freq. 3 hours	5 Minutes	Once the Memory reaches the configured threshold, Ceburu checks for the consistency of the spike with the interval set by the customer. If the spike is consistent for more than the interval set (>= interval set), Ceburu will send the first alarm mail to all the users assigned in the group for that alarm. Let’s say the spike starts at 10.00am and remains above the threshold level till 10.03am, the first mail will be sent. We flag the first mail as ‘WARNING’ email. At this stage, we add a trigger in the trigger table, which will be listed in the trigger page and the state was ‘Problem’. Auto Acknowledge: If none of the users acknowledges the trigger, Ceburu waits for 3 hours(user selected frequency) and auto acknowledge the trigger and assign it to ‘auto-usergroup users’ of the company. For e.g. If the spike reaches the threshold at 06.00am, first email will be send at 06.03am. If none of the users acknowledge, Ceburu auto-acknowledge at 09.03 and send out the email. If Memory usage drops below the threshold, the system waits for 5 minutes. If usage remains below the threshold for that duration, the issue is marked as resolved, and the trigger state changes from 'Problem' to 'Resolved.' If the issue is fixed and ‘Closed’, Ceburu will close the trigger, and change the state from ‘Problem’ to ‘Resolved’ and send the email for ‘auto-usergroup users’. If the issue is not fixed, Ceburu sent the follow-up ‘Critical’ email at 09.03am the next day (after 24 hours). This will happen every day. This email also send to ‘auto-usergroup users’. Manual Acknowledge: User has to enter the hours user needs to fix the issue and click on the Acknowledged option. When the user changes the state to ‘Acknowledged’, Ceburu sends a mail to the user who acknowledge the trigger. Ceburu will not send follow-up emails to the users, till the agreed hours is reached. Once the issue is fixed, the acknowledged user or any one of the admins should come to this popup and change the trigger state to ‘Closed’ Ceburu sends a mail to the user who acknowledge the trigger. If the issue is not fixed within the agreed hours, Ceburu will send the follow-up email to the auto-user. From this point Ceburu will send follow up emails once in 24 hours to the auto-user Note: All above will happen ONLY if the Global Alarm setting is in ON state. OFF will not notify the users on any triggers, except if the Probe is down.
3	Disk Usage	Options for user 3 Minutes 5 Minutes 10 Minutes 15 Minutes 20 Minutes Selected 3 Minutes	Options for user 3 hours 6 hours 9 hours 15 hours 24 hours Selected 3 hours	User Selected Freq. 3 hours	5 Minutes	Once the Disk reaches the configured threshold, Ceburu checks for the consistency of the spike with the interval set by the customer. If the spike is consistent for more than the interval set (>= interval set), Ceburu will send the first alarm mail to all the users assigned in the group for that alarm. Let’s say the spike starts at 10.00am and remains above the threshold level till 10.03am, the first mail will be sent. We flag the first mail as ‘WARNING’ email. At this stage, we add a trigger in the trigger table, which will be listed in the trigger page and the state was ‘Problem’. Auto Acknowledge: If none of the users acknowledges the trigger, Ceburu waits for 3 hours(user selected frequency) and auto acknowledge the trigger and assign it to ‘auto-usergroup users’ of the company. For e.g. If the spike reaches the threshold at 06.00am, first email will be send at 06.03am. If none of the users acknowledge, Ceburu auto-acknowledge at 09.03 and send out the email. If Disk usage drops below the threshold, the system waits for 5 minutes. If usage remains below the threshold for that duration, the issue is marked as resolved, and the trigger state changes from 'Problem' to 'Resolved.' If the issue is fixed and ‘Closed’, Ceburu will close the trigger, and change the state from ‘Problem’ to ‘Resolved’ and send the email for ‘auto-usergroup users’. If the issue is not fixed, Ceburu sent the follow-up ‘Critical’ email at 09.03am the next day (after 24 hours). This will happen every day. This email also send to ‘auto-usergroup users’. Manual Acknowledge: User has to enter the hours user needs to fix the issue and click on the Acknowledged option. When the user changes the state to ‘Acknowledged’, Ceburu sends a mail to the user who acknowledge the trigger. Ceburu will not send follow-up emails to the users, till the agreed hours is reached. Once the issue is fixed, the acknowledged user or any one of the admins should come to this popup and change the trigger state to ‘Closed’ Ceburu sends a mail to the user who acknowledge the trigger. If the issue is not fixed within the agreed hours, Ceburu will send the follow-up email to the auto-user. From this point Ceburu will send follow up emails once in 24 hours to the auto-user Note: All above will happen ONLY if the Global Alarm setting is in ON state. OFF will not notify the users on any triggers, except if the Probe is down.
4	System Up/Down	-	Default frequency 1 Day	-	-	Ceburu ping the systems every minute to check the UP/DOWN status. If the ping is not successful for 10 consequtive time, Ceburu decleare the system is in DOWN state. Ceburu will send a 'Critical' mail to all the users configured in the alarm page. At this stage, we add a trigger in the trigger table, which will be listed in the trigger page and the state was ‘Problem’. Follow up emails will be send same users configured in the alarm page once in 24 hours. Constantly Ceburu ping the system, even if it is down. When the ping is successful for 10 consequtive times, Ceburu will send a mail to 'auto-usergroup users' and close the trigger, and change the state from ‘Problem’ to ‘Resolved’ Note: All above will happen ONLY if the Global Alarm setting is in ON state. OFF will not notify the users on any triggers, except if the Probe is down.
5	Certificate Status		Default frequency 1 Day	-	-	Notify option is given for the user to set the number of days prior to the actual expiration date of any certificate Exactly on the date of notification (Expiration date - Notify period) Ceburu sends a mail to the users configured in the alarm configuration page. This mail will be send to the customer once in a day. When the certificate is renewaled, Ceburu will stop sending notification emails. Note: All above will happen ONLY if the Global Alarm setting is in ON state. OFF will not notify the users on any triggers, except if the Probe is down.
6	Probe Status	Default Interval 5 Minutes	Default frequency 1 Day	-	-	Ceburu constantly receives data from the probe. If there is a drop in receiving data (no data received) continuously for 5 minutes in Ceburu Agent & Ceburu Proxy, Ceburu sends a mail to these emails('zarek@ceburu.com', 'sjm@ceburu.com', 'k.massey@ceburu.com', 'sujan@seelogics.in', 'jonathsujan@seelogics.in',). Note: We will not check if Global Alarm Setting is ON or OFF.
7	Ceburu Agent	Default Interval 5 Minutes	Options for user 3 hours 6 hours 9 hours 15 hours 24 hours Selected 3 hours	-	-	Ceburu constantly receives data from the Ceburu agents If there is a drop in receiving data (no data received) continuously for 5 minutes in Ceburu Agent, Ceburu consider that the agent is down. Ceburu then sends an email to the users configured in the alarm page for this specific event. If the issue is not fixed, follow-up email will be sent to the company admin in the frequency(3 hours) set by the user. When the issue is resolved (started receiving data) Ceburu sends an email to 'auto-usergroup users' that the agent is UP again. Note: All above will happen ONLY if the Global Alarm setting is in ON state. OFF will not notify the users on any triggers, except if the Probe is down.
8	Ceburu Proxy	Default Interval 5 Minutes	Options for user 3 hours 6 hours 9 hours 15 hours 24 hours Selected 3 hours	-	-	Ceburu constantly receives data from the Ceburu Proxy If there is a drop in receiving data (no data received) continuously for 5 minutes in Ceburu Proxy, Ceburu consider that the agent is down. Ceburu then sends an email to the users configured in the alarm page for this specific event. If the issue is not fixed, follow-up email will be sent to the company admin in the frequency(3 hours) set by the user. When the issue is resolved (started receiving data) Ceburu sends an email to 'auto-usergroup users' that the Proxy is UP again. Note: All above will happen ONLY if the Global Alarm setting is in ON state. OFF will not notify the users on any triggers, except if the Probe is down.
9	Services	-	Default frequency 1 Day	-	-	If the service is down ceburu will send the email immediatly. Ceburu then sends an email to the users configured in the alarm page. This mail will be send to the customer once in a day. And the service is up ceburu will send the email immediatly. Ceburu then sends an email to 'auto-usergroup users'. Note: All above will happen ONLY if the Global Alarm setting is in ON state. OFF will not notify the users on any triggers, except if the Probe is down.
10