microsoft / microsoft/durabletask-netherite
Include child instance IDs in execution history
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 239
- Forks
- 37
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 2
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the limitation in Durable Function Monitor using a Netherite-backed durable function app, focusing on the Execution History Table and graphical view. Done means child instance IDs are browseable and nested execution relationships are represented, or the behavior is controllable through configuration if it cannot apply broadly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100