CloudBeat Docs
HomeRequest a DemoContactSign In
Search…
What is CloudBeat?
Get Started
Quick Start
Fundamentals
Creating Tests
Executing Tests
Managing Test Suites
Sample Projects
Introduction to Cloudbeat sample projects
Oxygen Cucumber project
Oxygen project
TestNG project
Features
Integrations
Supported Frameworks
Data-Driven Testing
CloudBeat Synthetic
What is CloudBeat Synthetic?
Creating your first monitor
Review general monitor results
Review specific monitor dashboard
Create SLA
Create Reports & Alerts
Changing Runtime Setting
Run Monitors
Maintenance
Incidents
Full Monitor Test - Example
Settings & Administration
Managing Notification Groups
Managing Permissions
Managing Users
Managing Account
Managing My Profile
References
Test Cases
Test Suites
Active Runs
Test Results
Environments
Apps
Releases
Projects
Reports
Common Scripts
Powered By GitBook
Incidents
Incidents allow you to track your monitors and find problems based on your desired conditions
To create Incidents for your monitor, head over to:
Monitoring -> Monitors -> Your Monitor -> Edit -> Policies -> ( + ) New Policy
Range type is based on your last number of runs / minutes / hours / days
Metric will determine your monitor / instance availability based on your desired percentage
Incident Severity will alert based on the severity, Unknown (No alerts) / Minor / Critical.
To set alerts, head over to: Reports & Alerts -> ( + ) Add Group
Resolve Automatically will stop the incident if no problems were founds.
​
​
CloudBeat Synthetic - Previous
Maintenance
Next - CloudBeat Synthetic
Full Monitor Test - Example
Last modified 1yr ago
Copy link