Skip to content

Conversation

@consideRatio
Copy link
Member

@consideRatio consideRatio commented Nov 18, 2025

I saw startup failures in a dashboard for a non-staging hub, but it was a false alarm. Even though I had selected one specific hub using a dashboard variable, I still saw other hubs startup failures in the server start failures panel. This PR fixes that!

Copy link
Collaborator

@jnywong jnywong left a comment

Choose a reason for hiding this comment

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

Nice catch! 🏈

@consideRatio consideRatio merged commit e3f1342 into jupyterhub:main Nov 18, 2025
3 checks passed
Copy link
Collaborator

@jnywong jnywong left a comment

Choose a reason for hiding this comment

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

Maybe add filter to a couple of other panels too?

sum(
# kube_pod_info.node identifies the pod node,
# while kube_pod_labels.node is the metrics exporter's node
kube_pod_info{node!=""}
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
kube_pod_info{node!="", namespace=~"$hub"}

Comment on lines 177 to 182
sum by (le) (
jupyterhub_server_spawn_duration_seconds_bucket
-
jupyterhub_server_spawn_duration_seconds_bucket
offset $__rate_interval
)
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
sum by (le) (
jupyterhub_server_spawn_duration_seconds_bucket{namespace=~"$hub"}
-
jupyterhub_server_spawn_duration_seconds_bucket{namespace=~"$hub"}
offset $__rate_interval
)

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants