Zejnilovic
commented
5 years ago Again my two cents for the preservation of the arguments because I remember being against it and the conversation not continuing:
Why I don't like it:
- there is not enough space on the landing page for it. And it is enough we have OPA like this, don't make landing page full of info that in the end, no one is going to read because there is too much of it.
- the statistics won't mean much if we don't take into account:
- is it the start/end of the month/week
- what actual day of the week it is
- is it scheduled job or job run by hand
- how recent the data is? is there a skew because we use statistics since last year, but now everyone switched the time they run their jobs, but it will not show for another year and in a year it will look like a normal distribution while showing nothing useful.
- I see the effect on the user as such:
- Oh look, I am running stuff at 7 AM and everybody else is running it at 7 AM, same as me. I should run my thing at 6:45 AM so my is first in the queue.
- I need to run something now, by hand, because I need it, I don't care about some histogram
- I have some scheduler setup. I just defined my data once, I don't look there any more if everything is working
Don't get me wrong, I am all up for monitoring, I have talked to @hamc17 about it already, but I am against showing it into Menas's landing page. I would rather define some boundaries/scope and have automated reports each weak.
Feature
Adding a histogram of standardization/conformance job's start times will allow to monitor peak loads. It will also encourage users to more evenly space their jobs when possible. Example
This statistics can be derived from mongodb run collection.