bluewave-labs
Custom Monitor Intervals
Custom Monitor Intervals
This issue addresses one of the feature requests mentioned in issue #2593 (point 7: Custom intervals)
Currently, HTTP(S) monitoring intervals are limited to a fixed set of options (1-5 minutes) in a dropdown menu. This limitation prevents users from setting more precise monitoring frequencies for different types of endpoints. Critical services might need more frequent checks (e.g., every 30 seconds), while less critical endpoints could be monitored less frequently to reduce system load.
Describe the solution you'd like Replace the current dropdown selection with an input field that allows users to specify custom monitoring intervals in seconds. The implementation would:
- Allow input of custom interval values in seconds
- Include validation for reasonable bounds (e.g., minimum 10 seconds, maximum 1 hour)
- Update the UI to display the input in seconds rather than minutes
- Maintain backward compatibility with existing monitors
During our last call we decided to add 15 seconds and 30 seconds only to the list. @Owaiseimdad
I'm monitoring apps that wake up on requests and go back to sleep after inactivity to save costs. I would like the monitor to wake them up only once per day. That is a big difference to each 30 seconds. I think allowing for custom values would be a better solution.
I'm monitoring apps that wake up on requests and go back to sleep after inactivity to save costs. I would like the monitor to wake them up only once per day. That is a big difference to each 30 seconds. I think allowing for custom values would be a better solution.
The problem with long custom monitoring durations is that it adds extra complexity as you need to select seconds, minutes or even hours in your case. However if anyone really is interested in this, happy to consider it in the future.
I'm monitoring apps that wake up on requests and go back to sleep after inactivity to save costs. I would like the monitor to wake them up only once per day. That is a big difference to each 30 seconds. I think allowing for custom values would be a better solution.
The problem with long custom monitoring durations is that it adds extra complexity as you need to select seconds, minutes or even hours in your case. However if anyone really is interested in this, happy to consider it in the future.
Why not just have the end user calculate whatever amount of time needed (in seconds) and have the interface reflect that time based on the seconds given? No need for a drop down, just a textbox and "apply" button.
Example (In seconds): 12600 -> Interface converts the front end to show 3 hr 30 min 3600 -> Interface converts the front end to show 1 hr 1800 -> Interface converts the front end to show 30 min 90 -> Interface converts the front end to show 1.5 min or 1min 30 sec 5 -> Interface converts the front end to show 5 sec
I imagine this would take out the complexity because you use a set standard (in seconds) to set the monitor value, then have the function count down in seconds from the given value and have the portal do a simple math equation to reflect the hours, min & sec based on that value.
@mohicody let me know if you are implementing this, happy to help here.
@gorkem-bwl I think this has been resolved. Let me know if I am missing anything?
@gorkem-bwl I think this has been resolved. Let me know if I am missing anything?
I dont think so. I didnt see a PR for this - or am I mistaken?
Oh okay apologies, I assume this is for same infra PR. Let me implement this and close then.