#orrc
void orbitBOT
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- orrc, 1 day ago, 10 messages
glacial radish
hi! not sure really, it's just how the dashboard works. Was there a particular problem you're trying to solve?
steady wyvern
It's just unexpected behaviour from the Dashboard.
I was investigating an alert from our backend, looked up the customer, and under "Events and logs" it only shows "200 OK" for all recent logs.
Clicking through to "View all" also didn't show any failures — but did show the successful invoice payment. The failure didn't show up either if I filtered logs by "Failed".
So the Dashboard made things more difficult — I had to dig further into the details to find the specific invoice, whose "Logs" section did show the "402 ERR".
It feels like a bug that only one of two near-identical HTTP requests would appear in the logs when filtering by the associated customer.
glacial radish
yeah the way this whole connecting/relating of objects and request logs work is not the greatest
steady wyvern
Alright. Is this then something that's known and might be improved? 🙂
It seems surprising that connecting the objects works fine for one request, but not another where essentially only the response code differs.