Skip to content

System log

The system log is the platform's error and event log: exceptions from the web portal, recorder service messages, integration failures, and other component-level events. It is stored in the database and viewed at Administration › Maintenance › System Log. Unlike the audit trail, which answers "who did what", the system log answers "what went wrong".

Reading the log

The All System Log tab lists entries newest first. Each entry has:

  • Severity — Critical, Error, Warning, Info, or Debug.
  • Date — when the event was recorded.
  • Source & Category — the component and code location that produced the entry (for example Web miarecweb.integrations.all.sso... for a web-portal SSO error).
  • Message — the event text; click through to see the full record, including the stack trace when one was captured.

Quick filters cover date range, severity, and source type; selected entries can be deleted. The Advanced Search tab combines criteria for more precise questions.

Retention

The Retention Settings tab controls automatic cleanup: Delete old system logs (Do not delete / Delete) and the retention period in days (minimum 30). With deletion off, the log grows until entries are deleted manually — on busy systems, set a retention period.

System log reports

Two report types turn the log into schedulable reports; they are created and run like any other report (see Global reports for operator specifics and the User Guide Reports chapter for the general workflow):

  • System Log Details Report — one row per log entry. Available columns: ID, Date/Time, Date, Time, Source, Location, Severity, Category, and Message.
  • System Log Summary Report — event counts (Total events) grouped by a time period: hour, day, week, month, or year. Use it to spot error spikes, then drill into the details report.
  • Log files — file-based logs of components that do not write to the system log.
  • System status — current health of the host, database, and services.
  • Audit trail — the user-activity counterpart.