A developer hosts a web application on a Windows-based Azure App Service. To troubleshoot intermittent database connection errors, the developer enables Application Logging (Filesystem) with a level of Verbose. Two days later, the developer notices that new log files are no longer appearing in the filesystem, even though the database connection errors are still occurring. Which of the following explains why the log files are no longer being generated?
- Application logging configured to use the local filesystem is automatically disabled by Azure after 12 hours.Cevap
- BThe App Service requires a Key Vault access policy to be configured to allow logs to be persistently written to the local storage environment.
- CThe local filesystem logging provider fails to initialize because a valid Application Insights connection string is missing from the configuration settings.
- DAn invalid Key Vault reference syntax within the App Configuration settings causes the logging framework's initialization pipeline to fail silently.
Cevap
Application logging configured to use the local filesystem is automatically disabled by Azure after 12 hours.
The correct option is correct because when you enable application logging to the filesystem in Azure App Service, Azure automatically disables this setting after 12 hours. This prevents the local disk space from filling up, especially under verbose logging levels. If persistent logging is required, application logs must be configured to write to Azure Blob Storage.
Adım Adım Çözüm
Anahtar Kavram
App Service application logs configured to the local filesystem are temporary and automatically turn off after 12 hours.