Audit logs and statistics

During use, the application automatically generates audit logs and statistical information, which are stored independently from the actual documents or workflows. The audit logs record all relevant changes to documents and workflows, e.g., status changes, processing steps, or system events.
In addition, statistics are generated that map usage data, process frequencies, or time sequences, and thus provide an overview of actual system behavior. Both the audit logs and the statistical data remain permanently in the database and can be read and further processed via the REST API.

The following metrics are recorded as statistics:

• Documents

  • Current number of available documents or templates

  • Uploaded to the database

  • Deleted from the database

  • Imported into the Viewer

  • Documents displayed in the Viewer

• Shared access

  • Current number

  • Created

  • Completed *

    • shared without authentication

    • shared with password authentication

    • shared with TAN procedure (email)

    • shared with TAN procedure (text message)

  • Canceled

    • shared without authentication

    • shared with password authentication

    • shared with TAN procedure (email)

    • shared with TAN procedure (text message)

• Workflows

  • Current number

  • Created

  • Completed

  • Canceled (processing was not begun) *

  • Canceled (some processing was performed) *

• Signatures

  • Total number

  • provided with mouse input

  • provided with touch input

  • provided with an electronic pen (not a stylus)

  • provided with click-to-sign

  • provided with a signotec signature pad

  • Qualified signatures using sign-me

• Messages sent via text message *

Archiving of statistics

Statistics recorded in the system grow continuously over time. This can cause queries to take noticeably longer as the amount of data increases. To counteract this, an archiving function can be activated via the setting jobs.statArchiveInterval. Even if automatic archiving is not enabled, statistics are archived when a user is actively removed.

Archiving consolidates raw statistical data within a defined period into condensed archive data. When querying statistics, this archive data is always used first. Data that extends beyond this period is automatically supplemented from the unprocessed raw data.

Optionally, older raw data can be deleted after a certain period of time using the setting jobs.statArchiveStatLifeTime to save storage space.