Closed pauldg closed 6 months ago
Looks great, but these new attributes are job specific, right? The way it is not, it is site specific. Or is it supposed to be like: When a submission of a job J of tool X is made, then TPV gets the attributes of each destination (which are specific to jobs of tool X) which then can be used in the logic?
They are aggregates across all past and current jobs submitted to a specific site/destination. The aggregates are not filtered for specific tools but could be if that's a requirement?
The query has now been moved to gxadmin: https://github.com/galaxyproject/gxadmin/pull/155
This PR addresses https://github.com/usegalaxy-eu/tpv-metascheduler-api/issues/6
Query added in example_tpv_config_locations_api.yml that retrieves historical statistics about job states per destination. Currently the query is filtered for .pulsar. destinations and a timefrane of 30 days.
An example request with the additional stats that will be sent to the API is in the README.md
TODO: