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

Ability to Configure Activity Reporting #471

Open
sdmichelini opened this issue Apr 9, 2024 · 1 comment · May be fixed by #473
Open

Ability to Configure Activity Reporting #471

sdmichelini opened this issue Apr 9, 2024 · 1 comment · May be fixed by #473

Comments

@sdmichelini
Copy link

Proposed change

Add ability to customize or disable activity reporting to the JupyterHub handler. Currently, all requests to the proxy get marked as activity. This means if you leave your browser open with an open tab that goes through the proxy and don't interact with the page your JupyterHub pod will not get culled!

Who would use this feature?

Anyone who wants to leverage JupyterHub pod culling that has a better was of detecting activity.

Copy link

welcome bot commented Apr 9, 2024

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! 🎉

sdmichelini added a commit to sdmichelini/jupyter-server-proxy that referenced this issue Apr 15, 2024
Allows proxy to be configured if it reports back
to JupyterHub. In some cases the proxy will always detect background
activity which means that the pod will never get culled. In
this case you must disable recording and use an alternative
source of activity(outside of this MR)

Closes jupyterhub#471
@sdmichelini sdmichelini linked a pull request Apr 15, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant