LinkOPSLinkOPS
13

History & audit trail

Every execution is recorded automatically — who ran what, on which device, when, and what came back. The history is your audit trail and your troubleshooting database.

13/17
  1. 1Open History to browse executions: command, device, trigger (manual / template / group / batch), duration, exit code and full output.
  2. 2Search and filter by device, command text or trigger type to narrow the view.
  3. 3Click any row to expand the full output — the complete terminal response is preserved, including ANSI colors.
  4. 4Export any filtered view to CSV for compliance reporting, team reviews or archival.
  5. 5The Logs page (separate from History) keeps application-level diagnostics — connection errors, startup events and internal warnings — for troubleshooting the app itself.
  6. 6From a session you can also download the terminal buffer as a .log file for a complete record of that session.

Tip

Export any filtered view to CSV for compliance or reporting — filter by date range, device or command first.

Note

History records include the exact command text, exit code, duration and the full output with timestamps — nothing is summarized or truncated.

// also in this category

Keeping devices healthy

How to use LinkOPS Desktop

A step-by-step walkthrough from the first install to running commands across your whole network.

Keeping devices healthy · // guide