Patch Schedules
Schedules automate patching during your maintenance windows.
Creating a Schedule
Click Create Schedule to open the wizard:
Step 1: Basics
- Name - Descriptive name (e.g., "Weekly Production Patching")
- Description - Optional details about this schedule
Step 2: Targets
Choose which servers to include:
- All servers - Entire fleet
- By environment - Production, Staging, etc.
- By tags - Custom tag matching
- By OS - Specific distributions
- By hostname - Pattern matching (e.g.,
web-*)
Step 3: Schedule
Configure when to run:
- Frequency - Daily, Weekly, Monthly, Custom
- Time - Specific time in your timezone
- Timezone - Select your local timezone
For custom schedules, use cron expressions:
# Every Sunday at 2 AM
0 2 * * 0
# First Saturday of each month at 3 AM
0 3 1-7 * 6
Step 4: Options
- Security only - Only apply security updates
- Reboot policy - Never, If Required, Always
- Failure threshold - Stop if X% of servers fail
- Stagger - Minutes between each server
Step 5: Notifications
- Webhook URL - Send notifications to Slack, Teams, etc.
- Email - Notify on completion or failure
Step 6: Review
Review all settings and click Create.
Managing Schedules
Schedule List
View all schedules with:
- Name and description
- Target summary
- Next run time
- Last run status
- Enable/disable toggle
Schedule Actions
| Action | Description |
|---|---|
| Edit | Modify schedule settings |
| Run Now | Execute immediately |
| Disable | Pause without deleting |
| Delete | Permanently remove |
Execution History
Click a schedule to view past runs:
- Run timestamp
- Duration
- Servers processed
- Success/failure counts
- Detailed logs
Schedule Best Practices
- Stagger production patches - Avoid patching all servers simultaneously
- Test in staging first - Run staging schedules before production
- Set failure thresholds - Stop if too many servers fail
- Configure notifications - Know immediately if something fails