Prometheus metrics endpoint #253

New Issue

Jef Roosens · 2022-06-17T09:30:18+02:00

Jef Roosens commented

2022-06-17 09:30:18 +02:00

I like metrics, so I want more metrics. Metrics showing how many requests are sent to the server, how many packages are currently in each arch-repo, how much space each one takes, build times etc. The list goes on.

Amount of requests
Time taken to process requests
build job metrics
repository size metrics
Separate query params from URL
Memory efficiency
Currently all values of a gauge get stored. This is not acceptable, and will cause long-running Vieter instances to very slowly start eating memory. Instead, only the various bucket values should be kept.

I like metrics, so I want *more metrics*. Metrics showing how many requests are sent to the server, how many packages are currently in each arch-repo, how much space each one takes, build times etc. The list goes on. - [x] Amount of requests - [x] Time taken to process requests - [ ] build job metrics - [ ] repository size metrics - [ ] Separate query params from URL - [ ] Memory efficiency Currently all values of a gauge get stored. This is not acceptable, and will cause long-running Vieter instances to very slowly start eating memory. Instead, only the various bucket values should be kept.

Jef Roosens added the

idea

label 2022-06-17 09:30:18 +02:00

Jef Roosens added this to the 0.6.0 milestone 2022-12-26 11:59:49 +01:00

~~Jef Roosens referenced this issue 2022-12-29 00:00:54 +01:00~~

Add Prometheus metrics endpoint #325

Jef Roosens added

enhancement

and removed

idea

labels 2023-01-03 21:51:37 +01:00

Jef Roosens commented