Feedback: 'Startup diagnostics' when it comes to Azure Functions with Azure Service Bus

[cquirosj]

Feedback for https://docs.particular.net/nservicebus/hosting/startup-diagnostics and https://docs.particular.net/nservicebus/hosting/azure-functions-service-bus/

In Azure Functions with Azure Service Bus, the way you configure an endpoint is by creating an instance of ServiceBusTriggeredEndpointConfiguration.

class Startup : FunctionsStartup
{
    public const string EndpointName = "MyFunctionsEndpoint";

    public override void Configure(IFunctionsHostBuilder builder)
    {
        builder.UseNServiceBus(() => new ServiceBusTriggeredEndpointConfiguration(EndpointName));
    }
}

ServiceBusTriggeredEndpointConfiguration has the .LogDiagnostics() method, however this class doesn’t have the method SetDiagnosticsPath mentioned in startup diagnosis documentation.

While using the "running the NServiceBus in Azure Functions (in-process)" sample code and after enabling LogDiagnostics, I do see the logging output in the console but I don’t see the file {endpointName}-configuration.txt being created. This is the case because, after all, this is a server-less function meant to be deployed server”less”, so there is no actual path the customer could look for the file, at least not when deployed only during local development.

We could have difficulties trying to have customers gather diagnosis information for us while troubleshooting support cases. Customers may get confused about the startup diagnosis not supporting what is stated in the docs. Especially since Azure Functions with Azure Service Bus documentation has a direct link to the startup diagnosis documentation