Dashboard
Platform

Restricting Testing Times

Restricted Time Windows are times during which all tests (Chaos Engineering experiments, Scenarios, and reliability tests) are disabled. This lets you prevent tests from running during critical times such as scheduled deployments and peak traffic times. Any tests scheduled to run during this time will be halted, and any tests running will also be halted once the window starts.

Note
You must be a Team Manager to create or edit Restricted Time Windows. See Role-based access controls for details.

Screenshot of the restricted time windows screen. There's a single window preventing tests between 12PM and 5PM on Mondays.

Creating a restricted time window

To create a new restricted time window:

  1. Open the Team Settings page by logging into the Gremlin web app, accessing Team Settings from the user menu in the top-right corner of the page, then selecting Restricted Times.
  2. Click Add Time Window. This opens a side pane where you can configure the time window.
  3. ^First, select which weekday(s) you want to set the window for. For example, if you want to set restrictions for Monday, Wednesday, and Friday, click on those two days.
  4. ^In the Window Start Hour field, enter the time that the restricted window will start.
  5. ^In the Window Length field, select how long the window will last. This is measured in hourly increments.
  6. ^In the Time Zone field, select whether to use your local time zone or UTC as a reference. This only changes the start time, but it's important to be aware of when selecting a start time.
  7. Click Save.

You can repeat these steps to add more time windows, up to a maximum of three (3) per day.

Editing a restricted time window to prevent tests on Sundays and Mondays between 12 and 2 PM.

Managing restricted time windows

You can edit an existing time window by clicking the Edit button next to it. You can also remove a window by clicking its Delete button. Note that deleting a time window is irreversible.

No items found.
Previous
Next
Previous
This is some text inside of a div block.
Compatibility
Installing the Gremlin Agent
Authenticating the Gremlin Agent
Configuring the Gremlin Agent
Managing the Gremlin Agent
User Management
Integrations
Health Checks
Notifications
Command Line Interface
Updating Gremlin
Quick Start Guide
Services and Dependencies
Detected Risks
Reliability Tests
Reliability Score
Targets
Experiments
Scenarios
GameDays
Overview
Deploying Failure Flags on AWS Lambda
Deploying Failure Flags on AWS ECS
Deploying Failure Flags on Kubernetes
Classes, methods, & attributes
API Keys
Examples
Container security
General
Linux
Windows
Chao
Helm
Glossary
Alfi
Additional Configuration for Helm
Amazon CloudWatch Health Check
AppDynamics Health Check
Application Level Fault Injection (ALFI)
Blackhole Experiment
CPU Experiment
Certificate Expiry
Custom Health Check
Custom Load Generator
DNS Experiment
Datadog Health Check
Disk Experiment
Dynatrace Health Check
Grafana Cloud Health Check
Grafana Cloud K6
IO Experiment
Install Gremlin on Kubernetes manually
Install Gremlin on OpenShift 4
Installing Gremlin on AWS - Configuring your VPC
Installing Gremlin on Kubernetes with Helm
Installing Gremlin on Windows
Installing Gremlin on a virtual machine
Installing the Failure Flags SDK
Jira
Latency Experiment
Memory Experiment
Network Tags
New Relic Health Check
Overview
Overview
Overview
Overview
Overview
Packet Loss Attack
PagerDuty Health Check
Preview: Gremlin in Kubernetes Restricted Networks
Private Network Integration Agent
Process Collection
Process Killer Experiment
Prometheus Health Check
Role Based Access Control
Running Failure Flags experiments
Scheduling Scenarios
Shared Scenarios
Shutdown Experiment
Slack
Teams
Time Travel Experiment
Troubleshooting Gremlin on OpenShift
User Authentication via SAML and Okta
Users
Webhooks
Integration Agent for Linux
Test Suites
Restricting Testing Times
Reports
Enabling DNS collection