Serverless computing in Azure with .NET

Diagnose

Detecting errors allows you to respond swiftly and fix issues before they have any significant impact. However, detecting is only half the story. To be able to effectively troubleshoot the issue, you need to be able to correctly diagnose what is causing it. As discussed in Chapter 8, Testing Your Azure Functions in the section on logging, there is nothing worse (from the troubleshooting standpoint) than getting a message along the lines of "A critical error has occurred".

The errors your report must provide enough context (meaningful messages, stack traces, and so on) to investigate where the error occurred and what could potentially be causing it. Good monitoring tools help in diagnosing the problem by allowing live data analysis. ...