The next tier up on monitoring is really to pass some unique ID through each URL that comprises the flow of checking a user's balance so that we can see for this specific inbound balance request that this was the result and delay at each step.
Not too hard, but a decent chunk of work — worth considering if the monitoring surfaces a not-tiny number of operations errors on the API side that we want solid data about.
The next tier up on monitoring is really to pass some unique ID through each URL that comprises the flow of checking a user's balance so that we can see for this specific inbound balance request that this was the result and delay at each step.
So, something like:
Initial call TwiML URL:
/get_balance?...transaction_id=myuniqueidgoeshere
Transcription success callback URL:/1510111222/1415111222/myuniqueidgoeshere/send_balance
Not too hard, but a decent chunk of work — worth considering if the monitoring surfaces a not-tiny number of operations errors on the API side that we want solid data about.