-
Task
-
Resolution: Unresolved
-
Minor
-
None
-
2.222.x
I came around two shortcomings of the AdministrativeError:
- One can push several time an AdministrativeError with the same id Jenkins will happily display all those monitors. But to manage the enable/disable status of a monitor, the Administrative monitor uses a Set which means that for a given id, either all the monitors are visible or none. This is true for any monitor btw.
- Once pushed, an AdministrativeError cannot be hidden easily by the end user: they need to POST to /<error_endpoint>/disable.
For 1, I'm not sure what the best approach would be. Probably ensuring the unicity of ids in Monitors by keeping a set of all monitors in addition to the set of disabled one. I don't really anticipate the impact this could have. Maybe someone as a good use case to use this shortcoming as a feature?
For 2, I guess we could simply enrich the AdministrativeError UI with a close button