DurableFunctionsMonitor 5.1.0

• Instance execution history can now be filtered by time and other field values:
  

• 'In' and 'Not In' filter operators. Filter values should be comma-separated or in form of a JSON array.

• Backend migrated to .Net Core 3.1.

• Direct requests that DfMon makes against Azure Table Storage now contain custom User-Agent header: DurableFunctionsMonitor-Standalone, DurableFunctionsMonitor-VsCodeExt or DurableFunctionsMonitor-Injected. Note that the majority of calls is still done via DurableClient, and those cannot be instrumented like this yet.

• Minor bugfixes.

durablefunctionsmonitor.dotnetbackend.5.1.1.nupkg
durablefunctionsmonitor-5.1.0.vsix

DurableFunctionsMonitor 5.0.0

• Now you can monitor Task Hubs from multiple Storage accounts with one single standalone instance. Specify alternative Storage connection strings via config settings prefixed with DFM_ALTERNATIVE_CONNECTION_STRING_, e.g. DFM_ALTERNATIVE_CONNECTION_STRING_my_second_conn, DFM_ALTERNATIVE_CONNECTION_STRING_my_third_conn etc. Then Task Hubs from those Storage accounts will become available under URLs like https://my-dfm-endpoint/my_second_conn-my-hub-name, https://my-dfm-endpoint/my_third_conn-my-hub-name etc.
  IMPORTANT: to restrict the list of Task Hubs exposed from those alternative Storage accounts, their names should be specified in DFM_HUB_NAME setting in the same format, e.g. my_second_conn-my-hub-name,my_third_conn-my-hub-name. If DFM_HUB_NAME setting is not configured, all Task Hubs from all configured Storage accounts are exposed.
• UI improvements for instance filter and in some other places.
• Minor bugfixes.

durablefunctionsmonitor.dotnetbackend.5.0.0.nupkg
durablefunctionsmonitor-5.0.0.vsix

DurableFunctionsMonitor 4.8.2

• Workaround for Azure/azure-functions-durable-extension#1926 (being unable to execute .Reset() and .StartNew() against a Task Hub named 'TestHubName').
• Reimplemented serving static files, to make it more secure.

durablefunctionsmonitor.dotnetbackend.4.8.2.nupkg
durablefunctionsmonitor-4.8.2.vsix

DurableFunctionsMonitor 4.8

• 'Start New Orchestration Instance' feature:

• VsCode extension should now work seamlessly in GitHub Codespaces.
• Full support for Microsoft SQL storage provider.
• Latest az-func-as-a-graph integrated.
• Minor bugfixes.

durablefunctionsmonitor.dotnetbackend.4.8.0.nupkg
durablefunctionsmonitor-4.8.0.vsix

DurableFunctionsMonitor 4.7.1

• Hotfix for incompatibility with Azure Storage emulator (#112).

durablefunctionsmonitor.dotnetbackend.4.7.1.nupkg
durablefunctionsmonitor-4.7.1.vsix

DurableFunctionsMonitor 4.7

• Latest az-func-as-a-graph integrated, and it is now used as yet another visualization tab for both search results and instance details, with instance counts and statuses rendered on top of it. So it now acts as an animated code map of your project:
  
  In VsCode ext the Functions Graph tab appears automatically once the relevant Functions project is open.
  To have this tab shown in standalone/injected mode upload the intermediate Functions Map JSON file to the underlying Storage Account. See instructions here.

• VsCode extension: 'Open XXXInstances/XXXHistory in Storage Explorer' menu items for Task Hubs:

• Long JSON (or just long error messages) can now be viewed in a popup window (#109).

• Minor bugfixes.

durablefunctionsmonitor.dotnetbackend.4.7.0.nupkg
durablefunctionsmonitor-4.7.0.vsix

DurableFunctionsMonitor 4.6

• New sortable Duration column to the list of results. Now you can quickly find quickest and longest instances.

• Gantt charts are now interactive (lines are clickable).

• VsCode extension: support for custom backends. You can now switch to a .Net Core 3.1 backend, or even to your own customized one:

  

• VsCode extension: (limited) support for Microsoft SQL storage provider. When you open a project that uses it, the relevant Task Hub should appear in the DURABLE FUNCTIONS view container:

  

  To connect to a MSSQL Task Hub in standalone mode use this custom backend.
  In 'injected' mode any storage provider should (theoretically) work.

• Minor bugfixes.

durablefunctionsmonitor.dotnetbackend.4.6.0.nupkg
durablefunctionsmonitor-4.6.0.vsix

DurableFunctionsMonitor 4.5

• Time can now be shown in local time zone:
  

• VsCode extension: F# support for Functions Graphs.

• VsCode extension: Instance Details tab is now integrated with Functions Graph. If relevant Functions project is currently open, the Details tab will allow navigating to Functions Graph and to Orchestration/Entity/Activity source code.

• Minor bugfixes.

durablefunctionsmonitor.dotnetbackend.4.5.0.nupkg
durablefunctionsmonitor-4.5.0.vsix

DurableFunctionsMonitor 4.4

• VsCode extension: now you can get a quick overview of any Azure Functions project in form of a graph. Command Palette -> Visualize Functions as a Graph.... For Durable Functions/Durable Entities the tool also tries to infer and show their relationships:
  

  Function nodes are clickable and lead to function's code.

• Minor bugfixes.

durablefunctionsmonitor.dotnetbackend.4.4.0.nupkg
durablefunctionsmonitor-4.4.0.vsix

DurableFunctionsMonitor 4.3

• Server-Directed Login Flow (aka cookie-based auth) is now not only supported, but also is the preferred one (because it's just better).
• All search/visualization params are now reflected in the query string, so you can share links with colleagues.
• Fixed time ranges ('Last Minute', 'Last Hour' etc.).
• Multiple choice for filtering by instance status ('Running', 'Completed' etc.).
• 'Not Equals', 'Not Starts With' and 'Not Contains' filter operators.
• Performance improvements.
• Minor bugfixes.

durablefunctionsmonitor.dotnetbackend.4.3.0.nupkg
durablefunctionsmonitor-4.3.0.vsix