Quick feedback for the Prometheus block

I like it a lot - it makes a runbook less dependent on external systems.

I hope that a future version of that block will also support a table view and perhaps even allow access to the results as a variable? I have a runbook for replacing the busiest worker in a Kubernetes cluster, and while it would be nice to see which one is the busiest in a table or graph, having its ID in a variable would make this even more useful.

One odd thing about the current Prometheus graph is the auto-refresh - the whole graph gets redrawn very visibly, like in slow motion.

1 Like

Glad you like it!

Absolutely planned. We released a bare-bones version to gauge interest, will absolutely extend with other data types + output saving :smiley:

I’ll get the auto refresh fixed. Thanks for reporting!

2 Likes

I’ve just made some tweaks to our prometheus block - will push the build tomorrow. It should be faster + the animations won’t be in the way any more

1 Like

These changes are out in v0.0.100

3 Likes