Log format
TRACE Sample Files
TRACE (.trace) files capture span-level timing and execution metadata. Use sample TRACE files to validate parser behavior and telemetry analysis workflows.
5 files
All to 1MB
SHA256 verified
Manifest included
Quick facts
Files first
Start with one representative file.
Starter file
DownloadDistributed Request Trace
Download Fixture| Filename | Size | MIME | Download |
|---|---|---|---|
| 354 B | application/octet-stream |
Download
|
|
| 1.0 MB | application/octet-stream |
Download
|
|
| 200.0 KB | application/octet-stream |
Download
|
|
| 500.0 KB | application/octet-stream |
Download
|
|
| 50.0 KB | application/octet-stream |
Download
|
No files match the current filter. Switch to another chip or size range.
Use cases
Pick the next task, not just the next file.
Use the file table first, then branch into compare or FAQ only if the task needs more context.
Compare and decide
Keep the next decision one step away.
FAQ and reference
Keep the operational details quiet.
Checksum Verification
Use checksums to confirm file integrity after download.
shasum -a 256 your_file_name_here
# Compare output with SHA256 values listed above.Where is the machine-readable manifest?
Use the manifest when you need stable names, SHA256 values, and URLs for automation.
Validation Methodology
- Validate extension and MIME detection before processing.
- Benchmark performance with small and larger files.
- Test malformed-input handling and error messaging.
Workflow Packs