Logs and diagnostics
Where the logs are
Section titled “Where the logs are”| Windows | Linux | Docker | |
|---|---|---|---|
| Central service | %ProgramData%\Routes\Central\Logs |
/var/log/routes/central, journalctl -u routes-central |
docker compose logs central |
| Node | %ProgramData%\Routes\Node\Logs |
/var/log/routes/node, journalctl -u routes-node |
docker compose logs node |
Logs roll daily and are kept 30 days. Errors also go to the Windows event log (sources Routes Central and Routes Node), and, if set, to a syslog server (Settings › Logging).
More detail for one problem
Section titled “More detail for one problem”Set LogLevel for the node to Debug (every tag in and out) or Verbose (bytes on the wire), then restart it:
under HKLM\SOFTWARE\Routes\Node on Windows, or Routes__Node__LogLevel on Linux and Docker.
Tools in the console
Section titled “Tools in the console”- Route tester (Configuration): which route a sender and header would take, and why the others do not.
- Echo and Test syntaxes (destinations): the connection, and what the destination accepts, from the central server.
- Check (DICOMweb destinations): a search with the credentials.
- Test (scripts and HL7 routing): run code or a sample message without saving.
- History: every instance and delivery, with the errors.
- Nodes: each queue’s last error, and node problems.
- Download (dead letters, quarantine): the file itself, to examine.
When asking for help
Section titled “When asking for help”Collect: what the sender, the router and the destination each say (their logs for the same time), the study’s history (History, opened), the node’s problems, and the version (Nodes tab). Remove patient data before sharing logs outside your organisation.