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
Jupyter doesn't have a way to capture enterprise gateway's client and kernel failures to be able to log them as events/metrics in the internal telemetry system. We would like to know
How many gateway client failures took place in the last few days corresponding to number of users
How many kernel failure took place.
Error/exceptions from Enterprise gateway.
Proposed Solution
By leveraging jupyter_events, we can emit events for both GatewayClient and GatewayMappingKernelManger. On the receiver side, having a server extension that listens all the events and log them to internal telemetry system.
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
Jupyter doesn't have a way to capture enterprise gateway's client and kernel failures to be able to log them as events/metrics in the internal telemetry system. We would like to know
Proposed Solution
By leveraging jupyter_events, we can emit events for both GatewayClient and GatewayMappingKernelManger. On the receiver side, having a server extension that listens all the events and log them to internal telemetry system.
The text was updated successfully, but these errors were encountered: