Currently the TracedEventKind enum does not provide any event for when a node is abruptly "cleaned" (i.e. its active requests are prematurely stopped).
We should emit a cleaning event that tells the users when a request has been stopped in this way, or else they might be confused about loose ends when trying to trace their message activity.
Currently the
TracedEventKindenum does not provide any event for when a node is abruptly "cleaned" (i.e. its active requests are prematurely stopped).We should emit a cleaning event that tells the users when a request has been stopped in this way, or else they might be confused about loose ends when trying to trace their message activity.