Feature request: (optionally) track usage of a resource instance

[jimklimov]

One of our use-cases for lockable resources is to dedicate actual physical devices used to test firmware builds. One side effect of these tests is writing to flash which eventually wears out, more or less predictably after just so many rewrites.

We would like to track at least how many times a lock for particular resource instance was given out, maybe with a further detail list to see who/what held it, when, how long. It would help us in some purchase planning, as well as to identify some outliers (e.g. notably slower devices) and on the coding side - to see how even the allocations distribution in this plugin really is (first listed and free? evenly random?)

Considering that there are also other use-cases for locks (e.g. dedicated virtual environments, or non-physical resources to sequentialise job runs as promoted in lock+milestone tricks), such book-keeping should be togglable by an additional flag field in the resource definition, off by default.

[eXtenZy]

I had a similar issue and created a Prometheus exporter that scrapes the REST API endpoint and exposes the state of the lockable resources status. You can get the usage by counting the locked and reserved states in Prometheus.

https://github.com/eXtenZy/lockable-resources-exporter

Hope it helps.