Twilio provides several tools for investigating the interaction between your application and Twilio. Debugger, Alerts, and Request Inspector the most commonly used tools that developers can use to quickly see how well their application is performing. Debugger and and Alters can be found in the Developer Center in Console:
Debugger contains a detailed log of activity within your application. This log can help you dive deeper and and understand what Twilio resources were impacted and by whom. A detailed log, such as the one exposed via Events can be useful in understanding the root cause of a problem.
Alerts allows you to find more information about requests that generated an error or warning.
Under the Alert Logs section, you will see a list of all the times your application has seen this error message. Click on the message you want to inspect to see full details about the request, response type, and the calls where this error happened.
The Request Inspector lists all requests made between Twilio and your application. You can find Request Inspector at the bottom of any call record, You can see this by going to Console > Programmable Voice > Logs > Calls and then clicking on the call you want to inspect. At the bottom will be Request Inspector.
To view your application’s response to a particular request, expand the ‘Response’ subheading under the request. Twilio stores these requests for 90 days from the time the call was created.</>
You can also use the Request Replay feature to replay a request and see a side-by-side difference between the saved request and the new request. The replayed request is identical to the original: Twilio will send all the same header and request information.
You can also play the request back against a different endpoint, so you can test a failed production request against your development server.