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
Currently the main method prometheus metrics are exposed for scraping is that they are served unauthenticated on the main port #344
If the notebook is exposed to the internet this obviously leaks a lot of information.
Proposed Solution
Jupyter server should support serving metrics unauthenticated on an alternate port eg. 9090. This pattern is used in most web services that export prometheus metrics.
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! 👋
Welcome to the Jupyter community! 🎉
dpeckett
changed the title
Should Support Serving Metrics On an Alternate Port
Support Serving Metrics On an Alternate Port
Aug 20, 2023
Problem
Currently the main method prometheus metrics are exposed for scraping is that they are served unauthenticated on the main port #344
If the notebook is exposed to the internet this obviously leaks a lot of information.
Proposed Solution
Jupyter server should support serving metrics unauthenticated on an alternate port eg. 9090. This pattern is used in most web services that export prometheus metrics.
The text was updated successfully, but these errors were encountered: