I'm sorry for not being explicit. The error is NOT logged in the Azure table. The issue is not with the KB. The issue is the error is absolutely, unequivocally, and in totality NOT put into the error table.
Although, I do completely agree with you that they should be logged to the error table. Because, that would be awesome. But they aren't.
Try and repro the issue and see what you find.
1) Clean SF in Azure Cloud Service w/ SQL Azure DB
2) Dummy controller that returns a view with a simple error. Something like "@using asdfasdf" should work.
4) Drop widget on page
Did you make any progress here?
I'm having the same issue. My app is stuck in the restarting loop. Without these logs I don't have a good place to start looking. Is there any way to turn this off and just have the logs write to the local file system?
We've successfully deployed a Sitefinity project to Azure, but we've decided to deploy to an Azure Web App instead of a classic Azure Cloud Service, which brings me to ask:
"How do we configure SItefinity to write diagnostic logs to Azure, i.e., storage container of our choosing?"
The documentation doesn't appear to include this minor detail. The steps I followed are posted here: docs.sitefinity.com/deploy-projects-to-azure-web-apps
Anyone have any idea how to configure a Sitefinity project to use Azure storage containers for diagnostics?