tree: af5b9fb05bd257621d4c81f7328e06ea05a7d3be [path history] [tgz]
  1. .allow-devtools-save
  2. .bowerrc
  3. .gitignore
  4. .travis.yml
  5. AUTHORS
  6. BUILD.gn
  7. LICENSE
  8. OWNERS
  9. PRESUBMIT.py
  10. README.md
  11. app.yaml
  12. bin/
  13. bower.json
  14. codereview.settings
  15. examples/
  16. hooks/
  17. images/
  18. run_dev_server
  19. run_tests
  20. skp_data/
  21. test_data/
  22. third_party/
  23. trace2html
  24. trace_viewer.gyp
  25. trace_viewer.gypi
  26. trace_viewer/
  27. vulcanize_trace_viewer
  28. why_imported
README.md

Build Status

Trace Viewer Logo

Trace-Viewer is the javascript frontend for Chrome about:tracing and Android systrace.

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:

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.

Contributing, quick version

We welcome contributions! To hack on this code, from toplevel: ./run_dev_server

In any browser, navigate to http://localhost:8003/

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.

Contact Us

Join our Google Groups: