Factory monitoring to capture submitted glideins #607
Description
This issue is being opened to ensure completeness for issue #520.
Issue 520 was addressed to cater to the Factory Ops team's requirement and as a result, the previously existing behavior of Factory monitoring ("Requested Idle Glideins" reflecting the number of submitted Glideins by the Factory and "Idle glideins" reflecting the actual number of Glideins in the Factory) was changed to "Requested Idle Glideins" reflecting the original request from the client, i.e. number of Glideins requested by the Frontend. While the change addressed the issue raised in 520, upon discussion, the GWMS development team decided that we will preserve the old behavior we were observing prior to the creation of issue 520, where "Requested Idle Glideins" line dips to zero once the Factory's Entry limits are reached.
Therefore, addressing this issue would result in three details to be captured/recorded for monitoring:
- Requested Idle Glideins → represents request coming from the frontend in each Factory cycle.
- Idle Glideins → represents the adjusted value calculated by the factory in each Factory cycle.
- Submitted Glideins (?; name undecided) → the new third value to be added representing the number of Glideins submitted by the Factory in each Factory cycle.
Additionally, the list of “Select elements to plot” should be updated in the monitoring page (factoryStatus.html) to indicate the annotations accurately once the new dip to zero behavior is also incorporated.
The first screenshot illustrates the current behavior (as a consequence of issue resolution for 520) and the second screenshot illustrates the prior behavior (at the time of opening issue 520).
