From 60d39b2f9923bf1b9d659f2f4dad223ec565466a Mon Sep 17 00:00:00 2001 From: Bryan Newbold Date: Thu, 10 Jan 2019 16:09:50 -0800 Subject: crude metrics integration (only a handful for now) --- notes/rust_libraries.txt | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) (limited to 'notes') diff --git a/notes/rust_libraries.txt b/notes/rust_libraries.txt index 7e6f33eb..d5c8c18a 100644 --- a/notes/rust_libraries.txt +++ b/notes/rust_libraries.txt @@ -8,6 +8,28 @@ libs: - cadence (emits statsd) - frank_jwt and JWT for (simple?) auth +metrics: +- best would be something with a configurable back-end, like 'log' for logging, + but supporing tags/labels. the prometheus model probably makes most sense by + default (really nice to be able to grab metrics with 'curl'/browser for + individual instances), but statsd seems to be what we run in production. not + spewing out lots of UDP by default seems like a good idea. +- dipstick: has all the good features, and popular, but code quality has smells + ("a32dlkjhw"-style commit messages), and API doesn't seem very clean. Also + prometheus stuff not actually implemented +- cadence: seems stable, somewhat popular, clean API. statsd-only for now, but + has custom backends that could be hooked on to. *super* few dependencies, + nice. +- tic: many deps; doesn't seem stable or under development +- rust-prometheus: developed by pingcap (large company). has push and pull + features. medum-sized deps; has feature flags + +A nice feature of a statsd solution is that collectd is usually running +locally (on linux dev, or in production), and metrics can be sent there by +default, like journald for logging. + +Seems like a decision between cadence (statsd) and rust-prometheus. + similar: - https://github.com/DavidBM/templic-backend - https://github.com/alexanderbanks/rust-api -- cgit v1.2.3