We have a sidecar that scrapes the +status page and exports metrics with a prometheus_client.
"status" would be helpful too.
Other than the contents of status page, we have disk usage metrics which is not really a devpi function.

On Fri, Apr 5, 2019 at 6:01 AM Florian Schulze <mail@florian-schulze.net> wrote:


On 5 Apr 2019, at 10:22, Stephan Erb wrote:

> Hi Florian,
>
> this is a great idea. We actually thought about implementing something
> like this but never had the chance yet.
>
> We are running Nginx in front of our Devpi instances and therefore
> already have sufficient Prometheus metrics coverage of HTTP requests,
> request latencies, etc.  What would still be helpful:
>
> * The master serial, current serial, and processed event serial. This
> would allow us to easily alert on lagging replicas.
> * The number of keyfs cache hits and cache misses so that we know when
> to tune the keyfs-cache-size

I thought of the above myself.

> * Some internal counters to figure out when and how often we are
> running into expired mirror caches.

Could you elaborate on this?

All the above would be possible solely from a plugin, so I think I will
go that route first.

Regards,
Florian Schulze
_______________________________________________
devpi-dev mailing list -- devpi-dev@python.org
To unsubscribe send an email to devpi-dev-leave@python.org
https://mail.python.org/mailman3/lists/devpi-dev.python.org/


--
Regards
Venkatesh
Email venkatesh.thirumale@gmail.com
Mobile: 857 272 2125