Prometheus metrics for the machine-learning service #31734
Replies: 3 comments
This comment has been hidden.
This comment has been hidden.
|
Pretty sure this one isn't a duplicate — I searched both issues and discussions before filing and couldn't find anything asking for metrics on the machine-learning service. The closest thread is #28596 (HPA autoscaling), but that's a resolved support discussion, not a feature request. The monitoring docs themselves note that only the server container currently uses |
|
This discussion has automatically been closed as it is likely a duplicate. We get a lot of duplicate threads each day, which is why we ask you in the template to confirm that you searched for duplicates before opening one. If you're sure this is not a duplicate, please leave a comment and we will reopen the thread if necessary. |
Uh oh!
There was an error while loading. Please reload this page.
The monitoring docs note that only the server container currently uses
IMMICH_TELEMETRY_INCLUDE— any chance the machine-learning service could get metrics too?/metricson the ML container just 404s (tried on the current release image; there's no prometheus client in it at all).It would be really useful. ML is the part that eats the GPU, and when thumbnails or facial recognition are running slow I currently have no way to tell whether it's inference latency, a pile-up of requests, or models being loaded. Request duration and counts, queue depth, maybe which models are currently loaded — that's the graph I'm missing.
If this is welcome I'd be happy to try a PR. Something like a
MACHINE_LEARNING_METRICSsetting (the ML config already uses theMACHINE_LEARNING_prefix) that turns on a simple metrics endpoint.All reactions