tju-yxq opened a new issue, #3165:
URL: https://github.com/apache/rocketmq-dashboard/issues/3165
## Problem
Maintenance windows (alert silences) can only be created and ended. Once a
window is created, its schedule and scope cannot be changed.
The current UI exposes only an **End** action:
- If a maintenance window was created too short, the operator must end it
and create a new one.
- If a recurring window's time zone, weekdays, or recurrence end is wrong,
the operator must delete and recreate it.
- If the scope was too broad (for example, all instances instead of one
instance), recreating the window creates a new record and loses the original
creator information.
The backend also has no update endpoint: `AlertSilenceController` supports
list, create, and delete only.
## Expected behavior
- An administrator should be able to edit an existing maintenance window:
- start/end time;
- recurrence type, time zone, weekdays, and recurrence end;
- domain, rule, instance, and label scope;
- reason.
- Editing should reuse the same validation as creation:
- end after start;
- valid recurrence time zone and bounded window duration;
- required recurrence end and valid ISO weekdays;
- bounded labels and reason.
- The existing record ID and creator should be preserved.
- Updates should be recorded in the operation audit log as an alert-silence
update.
- The maintenance window list should provide an edit action that pre-fills
the existing form.
## Why this matters
During a real maintenance period, plans often move. Extending a window by
thirty minutes should be a normal edit, not a delete-and-recreate workflow that
risks a gap in alert suppression and loses record provenance.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
