Try the Free Technical Preview

Install

Read the Free terms before installing or using FIXTracer. Use Python 3.11 or 3.12 with pipx:

pipx install fixtracer==0.1.0a3
fixtracer version

Start with the sample log

Use a new local directory. Keep distinct filenames; existing outputs can be replaced. These commands use the bundled sample order. The sample contains test data, not customer or production data:

fixtracer sample --out synthetic.log
fixtracer extract synthetic.log --clordid E_1_f_fill_before_activation_CL_0 --out incident.log
fixtracer report incident.log --out report.html --json-out report.json

Open report.html in a current desktop Chrome, Edge, Firefox, or Safari browser. The report is self-contained and works offline. Review the broad lifecycle finding and four preview events. The free preview limits the details shown and redacts report data. FIX and anomaly coverage are incomplete.

JSON is optional: omit --json-out report.json if you only want HTML. To rebuild HTML from the packed JSON:

fixtracer render report.json --out rerendered.html

The JSON format can change between preview releases.

Try an approved local log

For a small log, use fixtracer report with its explicit file path. The report parser handles SOH-, pipe-, and space-delimited FIX, including prefixed or wrapped messages.

For larger logs, use the extraction example above with your filename and exact identifier. Extraction requires one complete message per physical line, a consistent delimiter, and a final CheckSum field with its trailing delimiter. Wrapped messages and suffixes after CheckSum are unsupported by extraction. The limits are 1 MiB per line and 10,000 matching messages.

Use --clordid, --orderid, or --execid. Multiple selectors use OR; extraction does not expand relationships. A narrow extract can omit order context. Use fixtracer extract --help for options.

Keep total report input at or below 5,000,000 bytes. Larger input triggers a warning; above 10,000,000 bytes, reports are refused by default. Check the extract size: the message cap does not enforce these byte limits.

Use internal or redacted logs only on machines and in directories approved by your organization. Core commands do not transmit FIX logs or telemetry. Installation may contact the package index. Treat generated files as sensitive; redaction does not guarantee anonymity. Review them before any approved sharing.

Feedback

[email protected]

Do not send or attach production logs.

For installation or support questions: [email protected].