-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Include child instance IDs in execution history #296
Comments
Just putting the link to the relevant discussion on DfMon's side: microsoft/DurableFunctionsMonitor#126 (comment) |
Instance Ids of suborchestrations are already included as part of the I think the problem may be that the DFMon implementation is not using the |
@sebastianburckhardt , DfMon does not do any 'reverse engineering' , when bound to Netherite. For Netherite DfMon falls back to Have a test Netherite-based orchestration like this: Running it locally, with Azurite as a storage and an Event Hub in Azure. Testing .GetStatusAsync() like this:
Here is the output:
You see, no child instanceId (which is supposed to be |
Thanks for the quick response! Indeed a mystery. Will try to figure it out. |
What seems to happen is that I was not aware that this is happening (the code that does this processing is not part of Netherite, it is in the DF extension). Here is the code that does it: Not sure why it does that. Seems unnecessarily complicated. |
@sebastianburckhardt does it make sense to raise an issue with the DF extension, then, if that's the root cause of this issue? |
Yes, I think the appropriate place to modify this would be the code I linked to above. |
Durable Function Monitor is a very useful tool for debugging durable function executions, but the functionality for durable function apps using netherite is limited. Unlike the default backend, you can't browse to child instances from the Execution History Table, and the graphical representations are limited to one level (i.e. only sub-orchestrations and activities triggered directly are displayed)
If it doesn't make sense to apply this across the board, enabling through a configuration would be great.
The text was updated successfully, but these errors were encountered: