Client.story
- Support collecting cluster-wide story for a key or stimulus ID
#5872
Labels
diagnostics
enhancement
Improve existing functionality or make things work better
good second issue
Clearly described, educational, but less trivial than "good first issue".
stability
Issue or feature related to cluster stability (e.g. deadlock)
Worker and Scheduler both support a
{Worker|Scheduler}.story}
method which filters the transition log and returns all events for a given key or stimulus ID. Often, to understand the story the entire cluster-wide history is relevant.The Client should support an API returning the story of the a key or stimulus ID.
Note: The log format for scheduler and worker events are still different.
Stimulus IDs on scheduler side only supported once #5849 is implemented
The text was updated successfully, but these errors were encountered: