Open anthonychu opened 3 years ago
By "rollout is expected to complete in a few days," do you mean it will be in Azure production instances? What will the procedure be to change to the new version? (EDIT: Disregard second question: https://docs.microsoft.com/en-us/azure/azure-functions/functions-versions?tabs=csharp%2Cv4#changing-version-of-apps-in-azure)
That’s correct. The rollout is actually almost complete.
Note that, in addition to updating the extension version, you need to enable .NET 6 if your app is on Windows: https://docs.microsoft.com/en-us/azure/azure-functions/functions-versions?tabs=csharp%2Cv4#migrating-from-3x-to-4x
@anthonychu good call out, thank you. I know I was a squeaky wheel about rolling out with the new bits in January, and this has been awesome as we get to .NET 6. Kudos to you and your team!
@anthonychu After adding extension reference (Also we have already enabled .NET 6 by executing the following command "az functionapp config set --net-framework-version v6.0 -n
Functions runtime error Microsoft.Azure.WebJobs.Extensions.ApplicationInsights: Could not load file or assembly 'Microsoft.Azure.WebJobs.Logging.ApplicationInsights, Version=3.0.27.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. The system cannot find the file specified.
So when I switched over to the new extension, the blades like Performance and Failures have stopped working (nothing is displayed) when they previously were. The Live Metrics blade is still working though.
I have a handful of Http, Event, and Timer triggered v4 Functions running with C# .NET 6.
@feltocraig do you see data if you go directly to Application Insights?
Moot issue. The host.json had the default loglevel set as "None". I changed it to "Information". I'm guessing it's now being respected properly.
"logging": { "logLevel": { "default": "None" } }
@vikramdadwal did you find a solution ? experiencing a similar issue after trying "Microsoft.NET.Sdk.Functions" "4.0.1". Only in Azure, works fine local dev (previously it ran fine on "Microsoft.NET.Sdk.Functions" "4.0.0".)
@jedjohan : So after performing the following nuget updates , it started working:
But our organization build pipelines are now complaining the following as the hosts are not configured with "Preview" versions (so I am doing deployment from my local machine as CI/CD is broken for us):
@vikramdadwal Looks like you need to install .NET 6.x on the build agent using this task: https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/tool/dotnet-core-tool-installer?view=azure-devops
An update to the App Insights extension… based on some feedback and learnings during the preview period, we have decided to no longer require App Insights to be installed as an extension. A new version of the functions host with this change is deploying this week. There should be no disruption if you’ve already installed the preview App Insights extension. You’ll be able to remove the extension once the new host version is fully rolled out. We’ll post an announcement here shortly with more details.
@anthonychu good call on the app insights. I'm not crazy about having insights on downstream environments, so it's tricky when you want the same build to run everywhere but not necessarily with those bits.
@anthonychu : So does that mean if I revert the nuget change, and once the new host would be deployed this week, things will work fine.
Wohoo, now 4.0.1 of Microsoft.NET.Sdk.Functions works fine, with the explicit ref to Microsoft.Azure.WebJobs.Extensions.ApplicationInsights removed. Guess the hosting update reached West Europe 👍
Discussion for https://github.com/Azure/app-service-announcements/issues/348