Hi HN - I built this agent to make it easier to get feature distribution metrics into a Prometheus-Grafana observability stack when deploying with Tensorflow Serving.
The pain point this addresses is that TF Serving's default /metrics endpoint only exposes performance metrics (request size, request counts) but not metrics on the features or predictions, which is often interesting and valuable to monitor.
I'd argue that this is a resume overindexed on getting past recruiting filters looking for specific JavaScript libraries or UNIX commands. Even the recruiters action may not be necessarily bad - startups with a decided tech stack might decide they are not able to provide the time for a new hire to ramp up.
Effectively you penalise not catering the candidate resume to what you are looking for or deem important.
The pain point this addresses is that TF Serving's default /metrics endpoint only exposes performance metrics (request size, request counts) but not metrics on the features or predictions, which is often interesting and valuable to monitor.