wkpatrick

Ive been seeing a similar issue, where rutorrent is unable to connect to rtorrent for quite a while, before it graduates to taking several minutes to load before failing, and...

Did you make sure that the PromEx application is first in the children in application.ex? It will not catch the init events if it does not start before ecto/oban/etc.

> Correct, I had the exact same behavior, which I fixed by putting PromEx as the first child to be started.

@yordis The ecto dashboard parses the repo name out of the init metrics `label_values(_prom_ex_ecto_repo_init_status_info, repo)` Which are event based and defined here: https://github.com/akoutmos/prom_ex/blob/6a002fb029cf00eeadfcfef7ce984cd7a0f83493/lib/prom_ex/plugins/ecto.ex#L74 The event is only fired once when...

Nope. _prom_ex_ecto_repo_init_status_info is only filled on init. Other metrics contain the repo name, but only init_status_info is parsed to generate the labels in the dashboard.

Im running off of memory here when I was looking into this a while back, but I believe source_unavailable is for inserts. Ecto does not set the source on inserts.