Folders and files

Name		Name	Last commit message	Last commit date
Latest commit History 227 Commits
.github/workflows		.github/workflows
src		src
tests		tests
.gitignore		.gitignore
CLAUDE.md		CLAUDE.md
CODE_OF_CONDUCT.md		CODE_OF_CONDUCT.md
CONTRIBUTING.md		CONTRIBUTING.md
Cargo.lock		Cargo.lock
Cargo.toml		Cargo.toml
LICENSE		LICENSE
README.md		README.md
plan.txt		plan.txt
pyproject.toml		pyproject.toml

Repository files navigation

tlparse: Parse structured PT2 logs

tlparse parses structured torch trace logs and outputs HTML files analyzing data.

Quick start:Run PT2 with the TORCH_TRACE environment variable set:

TORCH_TRACE=/tmp/my_traced_log_dir example.py

Feed input into tlparse:

tlparse /tmp/my_traced_log_dir -o tl_out/

Adding custom parsers

You can extend tlparse with custom parsers which take existing structured log data and output any file. To do so, first implement StructuredLogParser with your own trait:

pubstructMyCustomParser;implStructuredLogParserforMyCustomParser{fnname(&self) ->&'staticstr{"my_custom_parser"}fnget_metadata<'e>(&self,e:&'eEnvelope) ->Option<Metadata<'e>>{// Get required metadata from the Envelope.// You'll need to update Envelope with your custom Metadata if you need new types here        ....}fnparse<'e>(&self,lineno:usize,metadata:Metadata<'e>,_rank:Option<u32>,compile_id:&Option<CompileId>,payload:&str) -> anyhow::Result<ParserResult>{// Use the metadata and payload however you'd like// Return either a ParserOutput::File(filename, payload) or ParserOutput::Link(name, url)}}