It provides rich analysis and visualization capabilities for many types of trace files. Its particularly good at viewing linux kernel traces (aka ftrace) and Chrome's trace_event format. Trace viewer can be embedded as a component in your own code, or used from a plain checkout to turn trace files into standalone, emailable HTML files from the commandline:
./tracing/trace2html my_trace.json --output=my_trace.html && open my_trace.html
Its easy to extend trace viewer to support your favorite trace format, or add domain specific visualizations to the UI to simplify drilling down into complex data.
We welcome contributions! To hack on this code, from toplevel: ./tracing/run_dev_server
In any browser, navigate to http://localhost:8003/
To run all python unittests: ./tracing/run_py_tests
To run all tracing unittests in d8 environment: ./tracing/run_d8_tests
To run all the unittests, you can also do:
Make sure tests pass before sending us changelist. We use rietveld for codereview. For more details, esp on rietveld, read our contributing guide or check out the trace viewer wiki.
Join our Google Groups: