It looks like Farmer takes the same storage account specified for AzureWebJobsStorage and automatically also uses it for the AzureWebJobsDashboard app setting:
When I deploy a function app from a Farmer app that generates this setting, I get the following logs in Application Insights when functions are executed:
Optional storage account connection string for storing logs and displaying them in the Monitor tab in the portal. This setting is only valid for apps that target version 1.x of the Azure Functions runtime.
as well as:
For better performance and experience, runtime version 2.x and later versions use APPINSIGHTS_INSTRUMENTATIONKEY and App Insights for monitoring instead of AzureWebJobsDashboard.
It seems it would be better to either:
Omit the AzureWebJobsDashboard setting completely (considering the latest Functions runtime version is 4.x)
Or, if compatibility with 1.x is still important, conditionally generate AzureWebJobsDashboard only when the chosen runtime is Functions 1.x
It looks like Farmer takes the same storage account specified for
AzureWebJobsStorageand automatically also uses it for theAzureWebJobsDashboardapp setting:https://github.com/CompositionalIT/farmer/blob/7d3d4e82f051aec6ac14c8bd41edd23e794913c7/src/Farmer/Builders/Builders.Functions.fs#L215-L216
When I deploy a function app from a Farmer app that generates this setting, I get the following logs in Application Insights when functions are executed:
and the guidance at that URL says:
as well as:
It seems it would be better to either:
AzureWebJobsDashboardsetting completely (considering the latest Functions runtime version is 4.x)AzureWebJobsDashboardonly when the chosen runtime is Functions 1.xI'd be happy to submit a PR for either solution.