Ben Sheldon [he/him]

@jejacks0n so happy you opened up this issue! I've been helping maintain Vanity for a minute :-) I'm really excited about seeing a slimmer, more contemporary, Rails-specific product/design experimentation tool....

@jejacks0n ooh, that sounds really interesting. I think adapter layers would solve some of the various challenges I've had with Vanity. Having thought about "what is my mental model" all...

@philipqnguyen yep, that's correct number of threads GoodJob will need from the database and the _minimum_ value you should safely have in your `database.yml`. I'm also recommending that people don't...

To cross-link efforts: there is some good code cooking over in https://github.com/bensheldon/good_job/issues/1198

@jgrau no worries, the issue is still open and it's good to know more about the systems experiencing it 😓 I think the fairly simple solution would be to have...

Thanks for opening up #911. That is really helpful! Also, I feel bad because now that I'm seeing what I wrote in this issue I'm like "hmm, what was I...

> The easiest 'v0' starting point may be to wire up the existing metrics to a prometheus compatable http endpoint in the frontend piece. Maybe these should actually be available...

@ckdake could you pick 3 metrics from that list to start with? That would help me scope it down to an end-to-end implementation. Also, some idle musings on this topic:...

Thanks. I think that's 5 😆 And apologies for being super pedantic here, but want to surface the design questions to work through 😄 - "how many items are in...

@jtannas fyi, `rubygems.org` does an interesting thing using the `GoodJob::JobsFilter`'s queries: https://github.com/rubygems/rubygems.org/blob/63f6ba818aaa21138a82c7d57da8380d261c5193/app/jobs/good_job_statsd_job.rb#L4-L10 I want to share it, but also warn that I still consider those private objects, so subject to...