Quick Start Guide
Overview
- Purpose: To help new AlertOps administrators quickly configure core platform components and begin sending alerts.
- Audience: AlertOps administrators and technical users responsible for onboarding teams.
- Prerequisites:
- Owner
- App Admin Role
- Outcome: Users, groups, schedules, integrations, and manual alerts are successfully configured.
- Estimated Time: 20–30 minutes
Feature Explanation
This guide walks through the foundational AlertOps setup tasks required to setup alerting:
- Creating and managing users
- Configuring contact methods
- Creating groups and schedules
- Setting up integrations
- Manually triggering alerts for incident response
These steps establish the minimum configuration required for routing alerts to the right people at the right time.
Configuration Guide
Creating Users
00:00: This article explains how to create new users within the alert tops platform.
00:05: You will learn the step-by-step process for adding and configuring user details.
00:11: Click the Configuration menu to access system settings
00:16: Click the user's option to manage user accounts.
00:20: Click the add user button to start creating a new user.
00:25: Enter your email address in the email field.
00:29: Click and enter the First Name to input the user's first name.
00:34: Click and enter the Last Name to input the user's last name.
00:39: Select the user type to Define access level.
00:43: Select your role from the available options.
00:47: Click the submit button to save the new user information.
00:52: Once saved, you can click the EDIT button on the User's profile page to modify details.
00:58: Click the button to finalize changes.
- From the menu bar, click Configuration and select Users.
- On the Users page, click Add Users (top-right).
- Enter the following details:
- Username (must be unique)
- Official Email Address
- First Name and Last Name
- Select the User Type.
- Assign the appropriate Role.
- Click Submit.
Expected Result: The user is created and receives a login email to reset their password.
How to Verify:
- Confirm the user appears in the Users list.
- Verify the user receives the password reset email.
Troubleshooting:
- If the email is not received, verify spam filtering and email correctness.
- Ensure usernames are unique.
Editing User Information
- Navigate to Configuration → Users.
- Select the desired user.
- Update profile details, roles, group membership, or schedules as needed.
Adding Contact Methods
00:00: This article explains how to add contact methods within Alertops.
00:05: You will learn the step-by-step process to configure and save new contact details for your user profile.
00:11: Click the username menu on the dashboard to access profile options.
00:17: Click on "Profile" to open your user profile settings, where contact methods can be managed.
00:24: Scroll down and click on the "ADD CONTACT METHOD" button to start adding a new contact method to your profile.
00:32: Click on "Select Contact Method" to view available contact method options.
00:38: Select the desired method, for instance, the phone contact method option labeled "Phone-Official" to add an official phone number.
00:46: Enter your phone number in the field to update the contact method with the new number.
00:51: Click and set the Wait Time as desired.
00:55: Enable this button to specify retry attempts.
01:00: Enter the duration, such as "10", to specify how long Alertops waits before retrying.
01:06: Save the new contact method and complete the addition process.
- Open the user’s profile.
- Click Add Contact Method.
- Select a Contact Method:
- SMS
- Phone Call
- Push Notifications (via AlertOps mobile app)
- Enter the required contact details.
- Click the Green Checkmark to save.
Expected Result: The contact method is available for alert routing.
How to Verify:
- Trigger a test alert to the user.
Creating Groups
00:00: This article explains how to create an edit groups within the alertops platform.
00:06: You will learn the steps to add a new group and update its details.
00:10: Begin by accessing the Alertops dashboard, where you can manage your groups and schedules.
00:17: Click on the 'Groups and Schedules' section to continue.
00:21: Click the add group button to start creating a new group within the platform.
00:27: Enter the name of the group, such as 'Platform Support', to identify the group's purpose.
00:33: Click the submit button to save the new group and add it to your list of groups.
00:39: Click the 'EDIT' option next to the group you want to modify to update its details.
00:45: Click in the description field to add or change the group's description for clarity.
00:50: Click the done button, to save your changes and finalize, the group editing process.
- Navigate to Configuration → Groups & Schedules.
- Click Add Group.
- Enter a unique Group Name.
- (Optional) Enable Dynamic to auto-populate members by attributes.
- Click Submit.
Adding Users to a Group
00:00: This article explains how to add users to a group within the alert tops platform.
00:06: You will learn the necessary steps to configure group membership.
00:10: Click the Configuration menu to access system settings, where group management options are located.
00:17: Click on "Groups and Schedules" to view and manage existing groups and their associated schedules.
00:24: Click the group to open its management page for editing user membership.
00:29: Click on "Add Members" to add or modify users within the selected group.
00:36: Click the user selection field, to begin adding a new user to the group.
00:41: Click the arrow right button to move forward in the group user Edition workflow.
00:47: Click the submit button to save the changes and add the user to the group.
- Select a group from Groups & Schedules.
- Open the Members
- Click Add Members.
- Move users from Available Users to Selected Members using the arrow.
- Click Submit.
Expected Result: Users are active members of the group.
Creating Schedules
- Open the desired group.
- Navigate to the Schedules
- Create one or more schedules as needed.
Note: Groups without schedules use the default member escalation sequence.
For detailed information, check out our guides on Managing Schedules
Creating an Escalation Policy
00:00: This article explains how to create a centralized escalation policy in alert tops.
00:06: You will learn how to configure priority levels, add member roles, and submit the policy for incident management.
00:13: Click the configuration menu to access system settings and options.
00:19: Select Escalation Policies to view and manage existing escalation rules.
00:25: Click on ADD ESCALATION POLICY to start creating a new escalation policy.
00:32: Enter your escalation policy name to identify it, such as infrastructure escalation.
00:38: Select a priority to choose the urgency level for this policy.
00:43: Enter a description for infrastructure, escalations to clarify the policy purpose.
00:49: Submit to save the new escalation policy and apply your settings.
00:54: In many cases, notification delivery needs to be consistent rather than personalized. In these situations, admins can set this up by toggling Centralized Rules in the Escalation Policy.
01:06: Click on EDIT to modify the selected centralized escalation policy details.
01:13: Click the Primary's input fields to set the initial escalation timing, retries, and intervals.
01:20: Add Member Roles to include roles responsible for escalation notifications.
01:26: Click the Secondary's input fields to set the initial escalation timing, retries, and intervals.
01:33: Submit to save all changes and finalize the centralized escalation policy.
- Navigate to Configuration → Escalation Policies.
- Click Add Escalation Policy (top-right).
- Enter a Policy Name.
- Select an AlertOps Priority.
- Add a Description for the escalation.
- Click Submit to save.
- Navigate to Rules
- Add Escalation Steps based on member roles.
- Configure wait times and retries.
- Add Communication channels.
- Preview the escalation policy steps by selecting the relevant Recipient Group.
Note: Recipient Groups are generally attached to an Integration and not directly to an Escalation policy.