10:13:47 <Ysean> mc_, is making v5 public, at this point, just a resource issue or is there still some work to be done on the code itself? I had in my mind that your commercial UCaaS was utilizing the v5 code for some time.  Is that correct?
16:30:46 <mc_> yes, our hosted platform and some clusters we manage are all on v5
16:31:06 <mc_> Ysean: the big hold up is on the app exchange
22:03:47 <Ysean> mc_: aaaaah.  That monster.
22:18:02 <mc_> yeah, it at least has a team on it now, so its moving less glacially
23:16:54 <ahmes_> Hi all - might anyone know how I can see potential API calls that failed through tapping into the AMQP queue?  I see the failed attempts in the debug log but I want to see if I can see exactly what is failing when it hits the API or what the attempted payload is.
23:21:30 <mc_> ahmes_: API requests mostly just log to the kazoo.log, but should log the request payload received and any log lines related to processing it
23:21:39 <mc_> the response should have a "request_id" you can use to grep the logs
23:21:42 <mc_> to see more details
23:25:01 <ahmes_> mc_: I see.   That helps. 
23:25:23 <ahmes_> It shows Msg-ID but not request_id
23:37:52 <mc_> AMQP messages have msg-id for logging purposes
23:38:29 <mc_> there are validators for each amqp payload that run before publishing and after reception (sender and receiver side)