|author||Loïc Hoguin <[email protected]>||2017-11-17 13:20:14 +0100|
|committer||Loïc Hoguin <[email protected]>||2017-11-17 13:23:38 +0100|
Initialize trace patterns only once
They are global for the node for all future call trace flags, so it's not necessary to set them repeatedly with every request. Doing it once at startup also ensures we can't have race conditions when the user wants to change which trace patterns should be used (because requests are concurrent and patterns end up overwriting themselves repeatedly), and makes this changing of trace patterns much more straightforward: the user can just define the ones they want. The default function traces everything. In addition I have also added the tracer_flags option to make the trace flags configurable, excluding the tracer pid.
Diffstat (limited to 'test/tracer_SUITE.erl')
1 files changed, 3 insertions, 0 deletions
diff --git a/test/tracer_SUITE.erl b/test/tracer_SUITE.erl
index 0f7fc5f..86ec9ac 100644
@@ -22,7 +22,10 @@
+%% We initialize trace patterns here. Appropriate would be in
+%% init_per_suite/1, but this works just as well.
%% We want tests for each group to execute sequentially