Azure-webjobs-sdk: AddDashboardLogging cannot be used at all

Created on 15 Oct 2018 · 3Comments · Source: Azure/azure-webjobs-sdk

While AddDashboardLogging says to be deprecated, it currently doesn't work at all with SDK 3.0. The cause is that only NullDashboardLoggingSetup is being registered and the actual DashboardLoggingSetup is only internal and therefor cannot be registered into the DI.

I also would like to express that the WebJobs Dashboard is very useful tool, especially for replaying and debugging WebJobs so I wouldn't really like to see it being deprecated or removed anytime soon.

Source

hajekj

👍10

Most helpful comment

Still hanging on to 2.0! Not being able to re-run functions in a dashboard really hurt us. It sounds like we are all going to have to write hand rolled APIs around running functions/webjobs. It was a killer feature for us because we dont have to wireup yet more code or handcraft service bus messages then send then via ServiceBusExplorer. This is also an issue with Azure functions.

ElvisLives on 10 Oct 2019

👍2

All 3 comments

Is there any comment here? Will this be fixed? This makes it impossible for us to upgrade to SDK v3.

kspearrin on 26 Feb 2019

👍1

This is a frustrating issue. I realise the API to add dashboard logging is marked as deprecated and the message is to use Application Insights instead.

However, having never really used Application Insights in anger, it's difficult to know how to get the invocation specific level of logging per function that was provided in the WebJob dashboard.

Is there a migration guide or some other documentation about how to configure App Insights to allow the same invocation/function specific logging to be found?

Also I'm assuming that once App Insights is enabled and configured appropriately for a WebJob, as App Insights is an all-encompassing solution for many different services, that there still won't be the ability to manually re-run specific functions in the same way we used to be able to do via the WebJob dashboard?