![nfs 2 se dashboard not appearing nfs 2 se dashboard not appearing](https://user-images.githubusercontent.com/1048514/91234028-b404b100-e6ef-11ea-98b2-2514230f6d40.png)
![nfs 2 se dashboard not appearing nfs 2 se dashboard not appearing](https://www.logicmonitor.com/wp-content/uploads/2015/12/Dashboard-Permissions.png)
So I just 'Upgraded' to v3.0.14 in an effort to keep our NuGet packages 'current' and I hit this same issue. Make sure that you have configured a connection string named AzureWebJobsStorage with a storage connection string. This may already be configured in Azure Portal if running WebJob udner existing app with App Insights.
![nfs 2 se dashboard not appearing nfs 2 se dashboard not appearing](https://www.stryder-it.de/simdashboard/Content/pages/index/hardware/dash1.jpg)
If this key exists in any config, use it to enable App Insights. Application Insights is recommended instead. The console output will continue to show in Kudu Dashboard, but functions will not be detected and won't be displayed, nor their invocations. However, from WebJobs SDK 3.x onwards, this is obsolete. This will work and show function invocations for WebJobs 1.x, 2.x. You can write to the Kudu Dashboard with var builder = new HostBuilder() The bulk of this worked fine in Framework 4.7, though the app builder was clearly different. If I go to the 'Functions' link in Kudu, it says there are no functions/function invocations to display. azurejobs/#/jobs/continuous/SubmissionJob shows Continuous WebJob Details SubmissionJobīut there's no list of function invocations below it, and the job remains permanently in a Running state. The Functions.cs has a method with the following signature: public async Task ProcessQueueMessageAsync( CloudQueueMessage incomingMessage, TextWriter log) Services.AddSingleton(new WebJobsActivator(services.BuildServiceProvider())) job activator, required in webjobs sdk 3+ Opts.UseSqlServer(("DefaultConnection"))) Ĭ("AzureQueueConnectionString"))) ConfigureServices((context, services) => If (!string.IsNullOrEmpty(appInsightsKey))ī.AddApplicationInsights(o => o.InstrumentationKey = appInsightsKey) Var appInsightsKey = context.Configuration If this key exists in any config, use it to enable App Insights Adding command line as a configuration source UseEnvironment(Environment.GetEnvironmentVariable("ASPNETCORE_ENVIRONMENT")) The Program.cs Program class looks like this: public static async Task Main(string args) D:\local\Temp\jobs\continuous\SubmissionJob\43ucb4rv.ipc>dotnet SubmissionJob.dll Which is odd, because the console output for the job does show it detecting a function: Run script 'run.cmd' with script host - 'WindowsScriptHost' It publishes fine, and runs, but doesn't show any Functions or list the Function Invocations on the dashboard. We have an Azure WebJob (3.x) running under an API App in Azure, all Core 2.1.