Thomas Orozco 87aed04d37 mononoke/sql_ext: publish SQL max open connections stat ... Summary: Like it says in the title, this adds support for publishing our max open connections to ODS. Note that this is a little more involved than I would like for it to be, but there is no way to get direct access to this information. This means, we need to: - Expose how many open connections we have in flight (this is done earlier in this stack in the Rust MySQL bindings). - Periodically get this information out out for MySQL, put it in a timeseries. - Get the max out of said timeseries and publish it to a counter so that it can be fetched in ODS. This is what this diff does. Note that I've only done this for read pools, largely because I think they're the ones we tend to exhaust the most and I'd like to see if there is value in exposing those counters before I use them. We do the aggregation on a dedicated thread here. I contemplated making this a Tokio task, but I figured making it a thread would make it easier to see if it's misbehaving in any way (also: note that the SQL client allocates a bunch of threads already anyway). Reviewed By: HarveyHunt Differential Revision: D27678955 fbshipit-source-id: c7b386f3a182bae787d77e997d108d8a74a6402b		2021-04-13 03:05:23 -07:00
..
src	mononoke/sql_ext: publish SQL max open connections stat	2021-04-13 03:05:23 -07:00
tunables-derive	autocargo v1: changes to match autocargo v2 generation results.	2021-02-19 11:03:55 -08:00
Cargo.toml	third-party/rust: update futures	2021-03-04 06:42:55 -08:00