Siteimp Log Workbench
A browser-only support tool for formatting, inspecting, filtering, and saving Siteimp NDJSON logs locally.
Load a log
Paste NDJSON or open a .ndjson, .jsonl, .txt, or .log file.
Local workbench
Saved logs are stored in this browser only. Use this to keep several logs handy while you inspect a support case.
Formatted output
Log records
Valid records are formatted below. Invalid lines stay visible with their source line number and parser error.
Filters
Filter by event meaning, operation ID, validity, text, or a custom field path.
Custom field filters
Use dot paths for nested values, such as payload.website_key or payload.gap_anomaly.
Saved log compare
Compare mode
Compare two logs saved in the local workbench by record counts, event codes, operation IDs, interesting records, and validity.
Nothing formatted yet
Paste a log, open a local file, or choose a saved log from the local workbench.
Before copying records
Copied log records may still contain sensitive values. Review copied text before sending it to Siteimp support or sharing it anywhere else.
What this tool is for
Siteimp writes structured run logs as NDJSON: one JSON object per line. That makes logs predictable for the application, but it can make them awkward to inspect by hand when you are trying to understand what happened during a scan, monitoring run, support request, or app lifecycle event.
This workbench formats those logs into readable records, keeps original source line numbers visible, and adds filters for the fields that matter most during support: event code, operation ID, timestamps, sequence order, lifecycle metadata, and nested payload values.
Local-first by design
This page runs in your browser. Files are read locally by the browser and are not uploaded to Siteimp. Saved workbench logs use your browser's local storage on this device.
Local storage is useful because it lets you keep several logs open while you inspect them. It is not a permanent archive. You can clear saved logs from this page at any time.
Before sharing log records
Formatting a log makes it easier to read. It does not make the log safe to share automatically. Before sending records to support or copying them into another tool, review them for values such as file paths, internal URLs, machine names, tokens, IDs, customer data, usernames, or any other sensitive information.
Why operation IDs matter
Siteimp uses operation IDs to connect user-visible actions to the events they trigger. When available, an op_id can help trace a workflow from the button click that started it, through backend work, and into the InfoDock or support message that surfaced the result.
Not every record has an operation ID, and that is fine. Some events are global lifecycle events or scheduler ticks. But when an operation ID is present, it is often the fastest way to follow the thread.
Custom filters
Siteimp logs have a known structure, but this formatter also supports custom field filters. You can filter by a nested field path such as payload.website_key , payload.gap_anomaly , or payload.source .
Custom filters are intentionally simple in this first version. They are meant to help you narrow a log without turning this page into a full log analytics platform.
Compare mode
The first version of this workbench focuses on stable loading, saving, formatting, filtering, and copying. Compare mode is scaffolded as a future enhancement and will be added once the saved-log workflow has been tested with real support cases.