CloudBeat Docs
HomeRequest a DemoContactSign In
  • What is CloudBeat?
  • Get Started
    • Quick Start
  • SUPPORTED FRAMEWORKS
    • Java JUnit
    • .NET MSTest
    • Playwright (JS/TS)
  • Fundamentals
    • Creating Projects
    • Creating Environments
    • Creating Tests Cases
    • Running Tests Cases
    • Creating Tests Suites
    • Running Tests Suites
    • Creating Releases
    • Adding Apps
  • Sample Projects
    • Introduction to Cloudbeat sample projects
    • Oxygen Cucumber project
    • Oxygen project
    • TestNG project
  • Features
    • Integrations
      • CI/CD Pipeline
        • Jenkins
        • Azure DevOps
      • Cloud Providers
        • Genymotion
        • Applitools
        • Perfecto
    • Supported Frameworks
    • Data-Driven Testing
      • DDT - Oxygen Framework
  • 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
    • Active Runs
    • Test Results
    • Projects
      • Oxygen Project
      • Cucumber + Java Project
      • .Net Project
      • TestNG Project Setup
    • Reports
Powered by GitBook
On this page

Was this helpful?

  1. CloudBeat Synthetic

Maintenance

PreviousRun MonitorsNextIncidents

Last updated 4 years ago

Was this helpful?

Maintenance Windows allows you to set a maintenance schedule which will stop all monitor activity during the specified time, and automatically continue to run afterwards.

What is a maintenance?

It's a process which contains software preparation, problem identification and finding out about product configuration management.

• The problem identification process includes checking validity, examining it and coming up with a solution and finally getting all the required support to apply for modification.

• The platform migration process, which is used if software is needed to be ported to another platform without any change in functionality

So while these processes are active, active monitor tests may interfere with them, that's where Maintenance Windows comes in handy and provides the option to stop the chosen monitor tests at any desired time and resume them when needed.

Maintenance schedule has several options:

• Once, when you have a sudden and critical issue.

• Weekly and monthly for scheduled occasions such as software updates.

To set up maintenance head over to the Monitoring section and click on Maintenance:

Click on New Window, give it a meaningful name, and choose your desired frequency and save:

After saving, your preferences the maintenance will appear and you'll be able to modify it or delete it under ACTIONS