Azure error logs - Error in controller, see log for details

Hello Andrew,

I can agree with you that the UI of the Azure Storage Explorer might be have been changed and the screenshots from the KB article and the instructions we have provided may not apply to the current view. We are aware that this can happen and we have noted this in the KB article.

What I can suggest is that you refer to the Azure Storage Explorer documentation in order to get more details about the latest updates in the UI and how to work with it: http://storageexplorer.com/

In addition to this, the errors that are thrown in the controller of an MVC widget should be logged in the error log files and you should be able to review them when you download the logs from Azure.

Regards,
Sabrie Nedzhip
Telerik

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.

Hi Andrew,

We do not have any known issue about that. The error messages that occur in the MVC controllers should be logged in logs and you should be able to see the error details when you download the logs from Azure. Do you have the project running locally? Are the errors that occur in the controller are logged in the Errors.log file under ~/App_Data/Sitefinity/Logs folder? Is it an option for you to try this?

Regards,
Sabrie Nedzhip
Telerik

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.

3) Deploy

4) Drop widget on page

5) Viola!

Hello Andrew,

Is the error logged in the Error.log file when you run the project locally (not when the project is deployed on Azure)? Is it an option to try this out and let me know about the results? Does the issue reproduce only when the project is deployed on Azure?

Regards,
Sabrie Nedzhip
Telerik

Don't you people have a QA department? Would you like me to fix the bug for you as well?

Andrew,

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?

Nope, unfortunately not. The answer seems to be: If you deploy to Azure you don't get full logs. Make sure you ask the nice folks at Telerik though, they'll happily point you towards your own fingers as a solution.

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?