Skip to main content





Logging database and architecture

The logs enable you to monitor the performance and availability of the platform and your applications. Use them to troubleshoot the issues and to make decisions about maintenance tasks.

The OutSystems logging mechanism is highly scalable. It separates logs by types into multiple database tables, rotates logic that enables retention while preventing indefinite growth. The tables are optimized for the quick logging and simple consultations.

Logs in the OutSystems platform flow from the applications to the database through an asynchronous mechanism. Bulk writing is used to optimize performance and minimize disruption of the application logic. This enables the platform to automatically generate detailed logging information and efficiently save it.

Logs are generated in the applications running in the front-end servers or in the built-in Services that are part of the platform architecture. Once the logs are created, they are written to the local message queue of the front-end. In each front-end server, a Log Service reads logs from the message queue and writes them in bulk directly to the database.

It's important to note that the Log Service writes directly to the database tables, but Service Center consults only the database views.

This section of the documentation is an overview of the log architecture and provides the reference for the Log Service database views. If you need information about the tables in the database, you should inspect the database manually.

Articles in this Section

  • Was this article helpful?