Error 503 first byte timeout - only have the db context in the trace

[gerhard]

@adamstac wrote:

---

I found the trace for this request in Honeycomb, and while I can confirm the socket_error at the end, there is no db-related error, which means that the db is not the culprit here:

---

Notice how little of the entire 84.76s trace we can attribute to any specific component (Ecto in this case):

Apart from that very thin slice highlighted in green, we do not see what else is going on in this trace. I am wondering what else we would need to add / configure to see where the rest of the time in this request is spent @jerodsanto. Maybe this will help: 🎬 https://www.youtube.com/watch?v=4OBtc_eIKIE cc @kamilkowalski

[gerhard]

WDYT @jerodsanto? 👆

[gerhard]

Closing since there hasn't been any activity in 2 months.

We can always re-open if we need to.