Open joschi99 opened 3 months ago
Hello :)
I took the time to inspect the code of the mode concerned and I don't find where this issue could occures with the option --unit
itself. Can you provide us an example output with the --verbose
and --debug
options to help me understanding the problem?
nlabels should contains "hours" if the option --unit=h
is handled.
Looking at the mode code and I don't find there is any interaction between the --unit
option and the --timeframe
option. The ---timeframe
must be expressed in seconds and is not converted according to the unit provided in the --unit
option.
Hi @lucie-dubrunfaut,
I think this is my error. Probably the option --unit
is related only to the threshold job-execution-last and not also to the --timeframe
. In this case you can close the ticket
Hello :)
Yes, from what I've seen, the timeframe
option is only expressed in seconds and doesn't take into account the information provided in the unit
option. However, this could be a possible enhancement suggestion if it is blocking you, or at least make this more explicit in the help section.
I think it makes sense to extend the plugin to use the unit
also for the timeframe
, it's normally much easier to handle hours/days/weeks instead of seconds.
I'll notice this as an enhancement suggestion :)
The option --unit=h is not working, the value defined with --timeframe is still calculated in seconds, so it's not possible to define thresholds in hours, days or weeks.