Export formats
The tracker supports multiple export formats:JSON export
Export events as structured JSON:CSV export
Export events as CSV for spreadsheet analysis:Telemetry schema v2
All exported events use a standardized schema:Schema fields
Core fields
- schema_version: Always
2for the current schema - timestamp_ns: Nanosecond-precision timestamp
- event_type: Event type (
sample,allocation,oom, etc.) - collector: Source collector identifier
- sampling_interval_ms: Sampling interval in milliseconds
Process context
- pid: Process ID
- host: Hostname
- device_id: GPU device ID (or -1 for CPU)
Allocator metrics
- allocator_allocated_bytes: Bytes allocated by PyTorch/TensorFlow
- allocator_reserved_bytes: Bytes reserved by the allocator
- allocator_active_bytes: Currently active allocations
- allocator_inactive_bytes: Reserved but inactive memory
- allocator_change_bytes: Change since last event
Device metrics
- device_used_bytes: Total device memory in use
- device_free_bytes: Free device memory
- device_total_bytes: Total device memory
Contextual data
- context: User-defined context string
- metadata: Additional key-value metadata
Load and validate telemetry
Load exported telemetry files:CPU telemetry
Export CPU memory tracking:TensorFlow telemetry
Export TensorFlow memory tracking:Legacy format conversion
The telemetry loader supports legacy formats:Export profiler summaries
Export high-level profiling summaries:Timeline visualization
Extract and visualize memory timelines:Integration with monitoring systems
Export to monitoring systems:Statistics export
Export tracker statistics:Next steps
- Debug OOM errors with OOM recording
- Detect memory leaks with leak detection
- Learn about basic profiling to get started