Provide capability to configure route for durable functions monitor

[tomkerkhove]

Provide capability to configure route for durable functions monitor so that we can expose it on {default route prefix}/monitor where monitor is defined in the settings.

[scale-tone]

Today monitor is configurable via your CSPROJ-file with DurableFunctionsMonitorRoutePrefix setting (see package readme).

Configuring this via app settings would be great, but sadly it isn't possible - this value needs to be known at compile time (it is used by this MSBUILD target for "doctoring" function.json files after project build).

[scale-tone]

Is DurableFunctionsMonitorRoutePrefix setting what you were looking for, @tomkerkhove ?

[tomkerkhove]

It is still using the /api prefix then, but added this to the host.json:

  "extensions": {
    "http": {
      "routePrefix": ""
    }
  },

However, when we add new HTTP functions we'll now always need to add the /api prefix to the route which is less ideal but I get why we have to do it.

PS: feel free to enable GH Discussions for this kind of stuff :)

[scale-tone]

However, when we add new HTTP functions we'll now always need to add the /api prefix to the route which is less ideal but I get why we have to do it.

DurableFunctionsMonitorRoutePrefix is specifically designed to avoid doing that.
Once configured, DfMon should appear under /{my-route-prefix}/{DurableFunctionsMonitorRoutePrefix}.
If this is not what you're observing, then can you please post your CSPROJ file and your build output?

[tomkerkhove]

I didn't specify any prefix which is why api is added in front and the empty prefix was required

[scale-tone]

So @tomkerkhove , does the above resolve your issue? Or would you say something is still missing?

[tomkerkhove]

It's ok for now, thanks!