Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
None
Description
moved from https://github.com/gearpump/gearpump/issues/1987. The usage is to trace the problems of abnormal tasks (e.g. exceptions, low throughput, high latency) to its containing executors (e.g. wrong configuration) and running machines (e.g. bad network).
It's impractical to return the mapping of executor to task list in processor summary. A better idea is to add a rest call which returns the executor for a task on user demand (e.g. click a display location button)