Can't enable logging to the storage
See original GitHub issueTried to enable storage based logging. When saving changes/configuration for Logs, get the following error
Failed to update web app logs settings.
Failed to update web app logs settings for [functions app name]. There was an error processing your request. Please try again in a few moments.
Details: TIME Thursday, May 26, 2016, 10:10:30 AM CORRELATION IDS 8da84782-a547-4f03-af56-7d0d48f4c9a2
Issue Analytics
- State:
- Created 7 years ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
What is the Enable logging (troubleshooting) option?
Type of log file Subfolder Outlook 2013 Outlook 2010 Outlook 2007
Outlook Autodiscover Temp No Yes Yes
Exchange ActiveSync Temp/EASLogFiles Yes No No
Availability service Temp/OlkAS...
Read more >Can't enable Event Log - windows server 2012 r2
1. Have you tried to right-click the log in event viewer and enable it? · Yes of course. I tried that and it...
Read more >Enabling Amazon S3 server access logging
Choose Properties. In the Server access logging section, choose Edit. Under Server access logging, select Enable. For Target bucket, enter the name of...
Read more >Cannot enable logging. Policy document length breaking ...
When I was trying to enable access logs for my http api in the api gateway, I got an error saying “Cannot enable...
Read more >Enable Data Access audit logs
This guide explains how to enable or disable some or all Data Access audit logs in your Google Cloud projects, billing accounts, folders,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
David found the root cause for this and the fix is deploying in the next couple weeks.
I have this issue happening in Southeast Asia region. What is the root cause? I am seeing the same result mentioned above. CorrelationId: cdc0afb7-baa5-4278-a725-53aafa237c1b