<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
I recently tried tracing, and really couldn't figure out how to make
it work for my needs. What I would like to be able<br>
to do is to turn tracing on for particular modules/functions in my
top level app.erl module, rather than attach to a running<br>
application and starting tracing there. If that's already possible,
I couldn't find a way to do it. It would also be very, very<br>
helpful to see from where the function was called - I think someone
else has already requested that.<br>
<br>
Thanks,<br>
<br>
<br>
<div class="moz-cite-prefix">On 09/21/2015 03:52 AM, Lukas Larsson
wrote:<br>
</div>
<blockquote
cite="mid:CAPj+05MhQx0kguYpq=dNM37DL5Mo+ve3bkJQZT92NyJnvtx5MQ@mail.gmail.com"
type="cite">
<div dir="ltr">Hello everyone.
<div><br>
</div>
<div>As you may know, one of the OTP teams focus areas for the
coming year is make tracing better. At the moment we are
gathering ideas and attempting to put together a vision of
what we would like to have, before deciding what we can make. </div>
<div><br>
</div>
<div>I'm pretty sure that many of you have much more experience
with using Erlang tracing while developing and in production
than I do, which is we would love to have your input as to
what you would like to change about tracing.</div>
<div><br>
</div>
<div>To set the scope of the discussion, when I say tracing I
include; erlang tracing, dtrace/systemtap, trace outputs
(stdout/file/IP), filtering through match specs, sequence
tracing, tool integration (dbg, fprof, redbug, recon to
mention some) and probably more.</div>
<div><br>
</div>
<div>To start the discussion, here are a few of my ideas in no
particular order:</div>
<div> * Allow multiple tracers. Today only one port/process can
be the receiver of trace data.</div>
<div> * Create a couple of scalable high throughput tracing
output backends with different overflow mechanics. Today all
tracing is funneled through one bottleneck and has no overflow
handling at all.</div>
<div> * Expose vm probes (today dtrace probes) to the erlang
tracer.</div>
<div> * Better integration of dtrace/lttngt/systemtap into the
erlang trace.<br>
</div>
<div> * Allow the erlang tracer to be an Erlang callback
module. Today only ports/processes are allowed.</div>
<div> * Optimize trace output to file/ip. Maybe use something
like the Common Trace Format (<a moz-do-not-send="true"
href="http://git.efficios.com/?p=ctf.git;a=blob_plain;f=common-trace-format-specification.md;hb=master">http://git.efficios.com/?p=ctf.git;a=blob_plain;f=common-trace-format-specification.md;hb=master</a>),
instead of the term_to_binary that we have today.</div>
<div> * Write much much better documentation for dbg :)</div>
<div><br>
</div>
<div>We are looking for feedback from both beginners as well as
seasoned veterans to make erlang tracing the best it can be.
So if you have any thoughts or ideas, join the discussion to
make Erlang tracing better for you and everyone else.</div>
<div><br>
</div>
<div>Thanks in advance,</div>
<div>Lukas</div>
<div>Erlang/OTP team</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
erlang-questions mailing list
<a class="moz-txt-link-abbreviated" href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a>
<a class="moz-txt-link-freetext" href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a>
</pre>
</blockquote>
<br>
</body>
</html>