For our multi-tenant application with distributed design, which will be hosted on Azure, we are searching for a solution for logging and tracing.
These two topics, Troubleshooting Best Practices for Developing Windows Azure Applications and Enabling Diagnostics in Windows Azure, have already been covered. Exists a better alternative to this?
What are the best procedures and strategies for it, please? o A storage plan? • Is there a third-party or open-source technology that can assist us with this?
EDIT: There are two things we're seeking:
Where should we keep log data according to best practises for storage strategy? Since it's a multi-tenant, multi-tier application, should the data be kept distinct for each tenant's tier, combined, or is there another way to do it? How do we keep the information so that we can track each request that crossed many tiers individually?
a tool that aids in the analysis, filtering, sorting, and viewing of trace data Trace the flow of a single task that crossed numerous tiers, as the trace data size will be relatively large.
In an on-premises application with various layers, I have utilised System.Diagnostic with an XML listener (web app, service layer 1, service layer 2, etc). I next viewed the log data using Microsoft Service Trace Viewer. Numerous capabilities are supported by SVCTraceViewer, including the ability to combine log files from different tiers, display data graphically, track individual requests, etc.
So, an open source or third-party tool akin to Azure. That aids the support engineer in analysing the problem and finding a solution.