Threshold trigger should use real time definitions
Description
In the current state the trigger is based on threshold intervals that can be configured for each threshd group package. This is really uncomfortable because you can't see the threshd packages in the web UI on the one hand, so you have to check the threshd packages before (usually using the bash), and on the other hand you have to calculate then what trigger value is, eg. 1,3,7,24 minutes to configure a threshold in the UI.
I would suggest to work with a real time frame as trigger. Just write `5m`, `10s` or `1h` to set define it. This would really improve the usability and comprehensibility.
In the current state the trigger is based on threshold intervals that can be configured for each threshd group package.
This is really uncomfortable because you can't see the threshd packages in the web UI on the one hand, so you have to check the threshd packages before (usually using the bash), and on the other hand you have to calculate then what trigger value is, eg. 1,3,7,24 minutes to configure a threshold in the UI.
I would suggest to work with a real time frame as trigger. Just write `5m`, `10s` or `1h` to set define it. This would really improve the usability and comprehensibility.