RFE: Limiter on how far a downtime is booked into the future
Posted: Thu Sep 17, 2020 1:50 am
Ahoy folks,
Apologies as I am unclear on how to book an Request for Enhancement (RFE) for Nagios XI.
I believe the process for CORE is to log something on the project GitHub, but not aware of such a GH for XI.
Do "set me in the right direction" if there is some formal process for this.
To the point, we have now had at least two major PROD outages related to one of our users booking "extended downtimes" well into the future.
By this, the most recent example involves an end date in 3020(when we all have flying cars and warm our dinners with ray guns).
I understand from working with SUPP on a past case, there is underlying limits due to the underlying MariaDB layer.
Specifically, I have the SUPP note detailed (below).
To this end, I would request a RFE be considered to implement some sort of limiter on the "End time:" field on "Scheduled Downtime" section.
Admittedly user education is a factor in this, but an innocent user will not think of the impact of such an act (and there are no warnings in the actual Downtime scheduler screen).
Then, one day their (unhappy) Nagios XI admin comes knocking with some sad story about PROD outages, and extended OT, all due to a badly formed downtime definition.
Thus, please consider and advise on implementing this?
Thank you!
---
Timestamps in MariaDB have a maximum value of 2147483647, equivalent to 2038-01-19 05:14:07. This is due to the underlying 32-bit limitation. Using the function on a timestamp beyond this will result in NULL being returned. Use DATETIME as a storage type if you require dates beyond this.
Taken from here:
https://mariadb.com/kb/en/from_unixtime/
Apologies as I am unclear on how to book an Request for Enhancement (RFE) for Nagios XI.
I believe the process for CORE is to log something on the project GitHub, but not aware of such a GH for XI.
Do "set me in the right direction" if there is some formal process for this.
To the point, we have now had at least two major PROD outages related to one of our users booking "extended downtimes" well into the future.
By this, the most recent example involves an end date in 3020(when we all have flying cars and warm our dinners with ray guns).
I understand from working with SUPP on a past case, there is underlying limits due to the underlying MariaDB layer.
Specifically, I have the SUPP note detailed (below).
To this end, I would request a RFE be considered to implement some sort of limiter on the "End time:" field on "Scheduled Downtime" section.
Admittedly user education is a factor in this, but an innocent user will not think of the impact of such an act (and there are no warnings in the actual Downtime scheduler screen).
Then, one day their (unhappy) Nagios XI admin comes knocking with some sad story about PROD outages, and extended OT, all due to a badly formed downtime definition.
Thus, please consider and advise on implementing this?
Thank you!
---
Timestamps in MariaDB have a maximum value of 2147483647, equivalent to 2038-01-19 05:14:07. This is due to the underlying 32-bit limitation. Using the function on a timestamp beyond this will result in NULL being returned. Use DATETIME as a storage type if you require dates beyond this.
Taken from here:
https://mariadb.com/kb/en/from_unixtime/