Ben Sheldon [he/him]

For anyone wanting to make an attempt at this, please do the global navbar first (Jobs, Batches, Cron, Processes) and open a PR. I much prefer small, even incomplete implementations...

@jnunemaker I appreciate you working on this. I'm still thinking about this, but wanted to share the direction of those thoughts. I lean towards decoupling things, with the code design...

Thank you both for the ideas! I'm in agreement with @jnunemaker that keeping a separate stats table would probably be too hot for single rows to be kept updated. And...

This is really interesting! And totally makes sense that we should try to be as accurate as possible for calculating those durations) Some thoughts: - This makes a lot of...

> For latency, the problem is essentially not solvable; postgres lacks a "monotonic timestamp" function That's a bummer, but also makes sense that would likely be very difficult to implement...

@ollym thanks for reporting! That's strange because I would currently expect a `job` and `head_execution` to point to the same row in the database 🤔 Maybe if you're using `preserve_job_records...

I have been thinking about this, especially after https://github.com/bensheldon/good_job/discussions/1109 was recently suggested. I'm thinking that, once that secondary navbar exists, the content could be configured in the goodjob configuration e.g....

> Why would this need extra custom configuration? I guess I'm proposing _not_ putting the environment string in it by default, but making it simple for you to insert it...

@sparshalc thanks for tackling this! It looks like the table currently has a single column which then `.row` and `.col` elements. Can you please replace those with `td` elements so...

I think this looks good. Any ideas for how to make it fully reversible? (I realize it wasn't reversible before)