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
We are setting up a PeriodicCallback for this handler which is eventually consuming that CPU. The not so clear part is that this handler is not registered with any endpoint for Prometheus to scrape the data. So, maybe this is vestigial piece of code?
Proposed Solution
If this PrometheusHandler is not critical, maybe we can set default config of enable_prometheus_metrics to False.
If PrometheusHandler is indeed unusable in the current state, we need to fix it for Prometheus to be able to scrap the metric data.
The text was updated successfully, but these errors were encountered:
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋
Problem
It seems like
PrometheusHandler
is consuming CPU even when there is no activity. More discussion in discourse thread.We are setting up a PeriodicCallback for this handler which is eventually consuming that CPU. The not so clear part is that this handler is not registered with any endpoint for Prometheus to scrape the data. So, maybe this is vestigial piece of code?
Proposed Solution
If this
PrometheusHandler
is not critical, maybe we can set default config ofenable_prometheus_metrics
toFalse
.If
PrometheusHandler
is indeed unusable in the current state, we need to fix it for Prometheus to be able to scrap the metric data.The text was updated successfully, but these errors were encountered: