Richard van der Hoff 6e3fc657b4 Resource tracking for background processes ... This introduces a mechanism for tracking resource usage by background processes, along with an example of how it will be used. This will help address #3518, but more importantly will give us better insights into things which are happening but not being shown up by the request metrics. We *could* do this with Measure blocks, but: - I think having them pulled out as a completely separate metric class will make it easier to distinguish top-level processes from those which are nested. - I want to be able to report on in-flight background processes, and I don't think we want to do this for *all* Measure blocks.		2018-07-18 10:50:33 +01:00
..
__init__.py	run isort	2018-07-09 16:09:20 +10:00
background_process_metrics.py	Resource tracking for background processes	2018-07-18 10:50:33 +01:00
resource.py	Run Prometheus on a different port, optionally. (#3274)	2018-05-31 19:04:50 +10:00