You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With configurable-http-proxy version 4.4.0 just released, there is support for exposing prometheus metrics on a given port.
But, it is not obvious to me where to add annotations to help prometheus scrape this metrics.
The CHP/proxy pod should run in a single replica.
The CHP/proxy pod is exposed behind the k8s service named proxy-http if autohttps is enabled, or behind proxy-public if it isn't.
The hub pod's k8s service is annotated so the hub pod is scraped.
Option 1: We could apply the prometheus scraping annotations to either the proxy-http service or the proxy-public service depending on where its located.
Option 2: We could apply the prometheus scraping annotations to the proxy pod itself
Those are the viable options I think, and I'm not sure what makes sense or how the details work out.
Action points
Configure --metrics-port=<some-port> when starting configurable-http-proxy
With configurable-http-proxy version 4.4.0 just released, there is support for exposing prometheus metrics on a given port.
But, it is not obvious to me where to add annotations to help prometheus scrape this metrics.
proxy-http
if autohttps is enabled, or behindproxy-public
if it isn't.Option 1: We could apply the prometheus scraping annotations to either the proxy-http service or the proxy-public service depending on where its located.
Option 2: We could apply the prometheus scraping annotations to the proxy pod itself
Those are the viable options I think, and I'm not sure what makes sense or how the details work out.
Action points
--metrics-port=<some-port>
when startingconfigurable-http-proxy
Related
jupyterhub/configurable-http-proxy#314
zero-to-jupyterhub-k8s/jupyterhub/templates/hub/service.yaml
Lines 7 to 19 in 714a3d2
The text was updated successfully, but these errors were encountered: