Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maintenance windows: smarter scheduling #26948

Open
allenhouchins opened this issue Mar 7, 2025 · 1 comment
Open

Maintenance windows: smarter scheduling #26948

allenhouchins opened this issue Mar 7, 2025 · 1 comment
Labels
~dogfood Issue resulted from Fleet's product dogfooding.

Comments

@allenhouchins
Copy link
Member

allenhouchins commented Mar 7, 2025

  • @noahtalerman: User requested this because having all calendaring events occur on the same day can cause an increase in IT support tickets and risk downtime for a large number of employees at the same time.
    • @noahtalerman: Eventually, Fleet could schedule the events at varying times and varying days for each end user.
  • @noahtalerman: User requested this because Fleet schedules a new calendar event on the next Tuesday if the end user is still failing. They want the new calendar event to happen sooner.
  • @mikermcneil: Nice to have: it would help if the calendar event told you whether or not this was automatic maintenance taking over your computer, or something that you have to do yourself. But either way, the calendar got me to do it.
    • The risk is that people get used to never opening the calendar event, because they assume it's something IT is doing for them
    • One way to potentially help here is to configure (if configurable- otherwise, maybe try tweaking in code) the reschedule interval. Eg. if I didn't do it at 17:00, then at 17:30, if it rescheduled immediately (more or less) to be later that same day or early the next morning, it would have a stronger psychological effect (as an employee, you feel like you can't get away with ignoring it)

@allenhouchins allenhouchins added the :product Product Design department (shows up on 🦢 Drafting board) label Mar 7, 2025
@noahtalerman
Copy link
Member

Problem

Currently, the calendaring automation will schedule and reschedule its event if the issue is still not resolved on the following Tuesday. This means a device might remain in an undesirable state for an extended period of time.

https://fleetdm.slack.com/archives/C084F4MKYSJ/p1741274272877179

This also means that everyone is performing actions on the same day which could lead to an increase in IT support tickets and risking other down times. In some cases this could be hundreds or thousands of employees.

What have you tried?

N/A

Potential solutions

The automation should schedule calendaring events at the next available time slot starting at 24 hours after the policy has been evaluated for the device.

What is the expected workflow as a result of your proposal?

Calendaring automation events will be more distributed and users will get compliant or back in a desired state more quickly.

@noahtalerman noahtalerman changed the title Calendaring automation should always schedule and reschedule next day or next available time slot Maintenance windows improvements: smarter scheduling Mar 7, 2025
@noahtalerman noahtalerman added ~feature fest Will be reviewed at next Feature Fest ~dogfood Issue resulted from Fleet's product dogfooding. and removed :product Product Design department (shows up on 🦢 Drafting board) labels Mar 7, 2025
@noahtalerman noahtalerman changed the title Maintenance windows improvements: smarter scheduling Maintenance windows: smarter scheduling Mar 19, 2025
@lukeheath lukeheath moved this to Ready in 🍽️ Dogfood Mar 20, 2025
@noahtalerman noahtalerman removed the ~feature fest Will be reviewed at next Feature Fest label Mar 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
~dogfood Issue resulted from Fleet's product dogfooding.
Projects
None yet
Development

No branches or pull requests

2 participants