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

Allow users to opt out of prometheus metrics #124

Merged
merged 3 commits into from
Aug 23, 2022

Conversation

dleen
Copy link
Contributor

@dleen dleen commented Apr 6, 2022

Poor mans fix for #123

@welcome
Copy link

welcome bot commented Apr 6, 2022

Thanks for submitting your first pull request! You are awesome! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please make sure you followed the pull request template, as this will help us review your contribution more quickly.
welcome
You can meet the other Jovyans by joining our Discourse forum. There is also a intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

Copy link
Member

@kevin-bates kevin-bates left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @dleen - this LGTM and addresses an issue that multiple consumers are running into.

My only suggestion would be that it might be helpful to indicate at runtime (via a log message, DEBUG or INFO) that Prometheus metric collection has been disabled, but I'd be fine releasing without the messaging as well.

@dleen
Copy link
Contributor Author

dleen commented Aug 22, 2022

@kevin-bates good suggestion! done!

@dleen dleen force-pushed the master branch 2 times, most recently from 5cdc1ed to 2a39df8 Compare August 22, 2022 17:59
README.md Outdated Show resolved Hide resolved
@kevin-bates
Copy link
Member

Hi @jtpio - I'm hoping you might be able to give this PR some attention relative to its review/merge/release as it will alleviate some heartburn for others.

In looking into this, I found that the lint tooling must have changed over (I'm assuming) its last major release and have provided PR #138 to address the linting failures evident on the various PRs - so it might be helpful to review/merge that PR prior to others.

I you need help, or I should be reaching out to someone else, please let me know. Thank you.

dleen and others added 2 commits August 23, 2022 15:02
Co-authored-by: Kevin Bates <kbates4@gmail.com>
@jtpio
Copy link
Member

jtpio commented Aug 23, 2022

Thanks @kevin-bates for the ping, this looks good.

I used the GitHub button to rebase the branch to make sure to grab the fixes from #138:

image

Also this repo is compatible with the Jupyter Releaser so we can make a 0.6.2 release after merging this.

Actually @kevin-bates if you would like to make the release feel free to proceed. You should have publish access to PyPI already. And I can add you to npm if you give me your username (the JupyterLab extension is also published to npm for consistency): https://www.npmjs.com/package/@jupyter-server/resource-usage

@kevin-bates kevin-bates merged commit d6edf6a into jupyter-server:master Aug 23, 2022
@welcome
Copy link

welcome bot commented Aug 23, 2022

Congrats on your first merged pull request in this project! 🎉
congrats
Thank you for contributing, we are very proud of you! ❤️

@kevin-bates
Copy link
Member

Hi @jtpio. I'm sorry, I don't currently have the bandwidth to revisit the jupyter-releaser stuff (I've used it once, probably late last year) and wouldn't want to mess things up. If you're unable to get to this in the next couple of days, I could probably spend some time with it on Friday. FWIW, my npm username is kbates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants