Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Serving Metrics On an Alternate Port #1316

Open
dpeckett opened this issue Aug 20, 2023 · 1 comment
Open

Support Serving Metrics On an Alternate Port #1316

dpeckett opened this issue Aug 20, 2023 · 1 comment

Comments

@dpeckett
Copy link

dpeckett commented 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.

@welcome
Copy link

welcome bot commented Aug 20, 2023

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.
welcome
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 dpeckett changed the title Should Support Serving Metrics On an Alternate Port Support Serving Metrics On an Alternate Port Aug 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant