-
-
Notifications
You must be signed in to change notification settings - Fork 191
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
Improve Dashboard Charts (feedback welcome) #438
Comments
That would be awesome! When we faced configuration problems we saw the dashboard printing a chart of enqueued jobs, but not executed ones, so it seemed everything was in order at first. Of course we wouldn't rely on just the dashboard for this (see also #403) but in this particular case it would have helped.
We are printing some very basic charts internally and were having success using As for medians, if you look at the postgres implementation of |
@aried3r thanks for sharing that story about an incident. That's helpful to know these things have consequences. I'll check out Chart.js as an alternative to Chartist. I think I can do the minimum of what is needed without I think this is the feature I want "Line Datasets" for building a time-series-box-and-whisker-like plot: https://www.chartjs.org/docs/3.2.0/samples/area/line-datasets.html And thanks for pointing to |
Continuing to think and work on this. For context, Heroku has these time bucket options: I really would like to have a cumulative flow diagram. Some thoughts on what to show:
I dunno quite how to offer both a (Min, Avg, P95, Max)-breakdown, and Queue (or Job) -based breakdowns |
Thanks for GoodJob, it's an awesome tool! In the spirit of keeping the scope of this project down though, I wouldn't build a very advanced dashboard for it. Instead, just expose the relevant metrics (queue length, etc) and let other tools provide the dashboard. These other tools could be Grafana/Prometheus, Cronitor.io (we're about to integrate them with GoodJob right now), BetterUptime, etc. Better if this projects stays focused on the ruby/jobs side, ideally with only a simple HTML based dashboard (or only a JSON API with stats). Projects that spread themselves too thin tend to run into problems when the 1-2 maintainers enter a period in their life [family] with less time to allocate to an open-source project. On that topic, try to get more project team members onboard. Perhaps some of the existing contributors would be willing to help out (https://github.com/bensheldon/good_job/graphs/contributors). |
Some additional inspiration: |
I would love feedback on these charts:
Other charts?
I'd like to make these charts load asynchronously (SJR) so that the dashboard doesn't load too slowly.
The text was updated successfully, but these errors were encountered: