Example Sessions

First let’s trace the queue:new functions in any process:

----------------------------------------------------------
1> recon_trace:calls({queue, new, ’_’}, 1).
1
13:14:34.086078 <0.44.0> queue:new()
Recon tracer rate limit tripped.
----------------------------------------------------------

 The limit was set to 1 trace message at most, and recon let us know when that limit was reached.
 Let’s instead look for all the queue:in/2 calls, to see what it is we’re inserting in queues:

----------------------------------------------------------
2> recon_trace:calls({queue, in, 2}, 1).
1
13:14:55.365157 <0.44.0> queue:in(a, {[],[]})
Recon tracer rate limit tripped.
----------------------------------------------------------

 In order to see the content we want, we should change the trace patterns to use a fun that matches on all arguments in a list (_) and returns return_trace() . This last part will generate a second trace for each call that includes the return value:

----------------------------------------------------------
4> recon_trace:calls(
4> {queue, ’_’,
4> fun([A,_]) when is_list(A); is_integer(A) andalso A > 1 ->
4> return_trace()
4> end},
4> {10,100}
4> ).
32
13:24:21.324309 <0.38.0> queue:in(3, {[],[]})
13:24:21.371473 <0.38.0> queue:in/2 --> {[3],[]}
13:25:14.694865 <0.53.0> queue:split(4, {[10,9,8,7],[1,2,3,4,5,6]})
13:25:14.695194 <0.53.0> queue:split/2 --> {{[4,3,2],[1]},{[10,9,8,7],[5,6]}}
5> recon_trace:clear().
ok
----------------------------------------------------------

 Note that in the pattern above, no specific function (’_’ ) was matched against. Instead, the fun used restricted functions to those having two arguments, the first of which is either a list or an integer greater than 1.
 Be aware that extremely broad patterns with lax rate-limitting (or very high absolute limits) may impact your node’s stability in ways recon_trace cannot easily help you with. Similarly, tracing extremely large amounts of function calls (all of them, or all of io for example) can be risky if more trace messages are generated than any process on the node could ever handle, despite the precautions taken by the library.
 In doubt, start with the most restrictive tracing possible, with low limits, and progressively increase your scope.