Logging in OutSystems

Topics

● What is logged?
● Anatomy of an Error Detail
● Module Logging Configuration
● How Logging Works in OutSystems
What is logged?

● Errors
● General Audits (e.g. Developer-defined,
platform internals, slow queries)
● Web and Mobile Requests
● Integrations
○ SOAP and REST
○ Extensions
● Asynchronous Executions
○ Timers
○ SMS
○ Email
○ Processes
● Mobile Apps Generation
Application Errors
By default, OutSystems logs all application errors
Anatomy of an Error Detail

Errors (and other log messages) can be inspected in Service Center

When the error was logged

The application module where it occurred
The user id (if logged in)

Error message

Extra request information

(e.g. Request URL, HTTP Method)
Error Detail: Stack Trace

Stack trace may contain useful information about where (in the code) the error
occurred (e.g. Module, Screen, Action)

OSMDb Module
CreatePersonMovieRole
Entity Action
MainFlow UI Flow Save Screen Action
AddMovieParticipant Screen
Module Logging Configuration

Logging configuration can be tuned on a per-module basis

Enable/disable logging of general

log messages created by the
developers

Enable/disable logging of Screens,

Extensions and Integrations
How Logging Works in OutSystems

Table 0 Views
Table 1 OutSystems Services
Service Center OutSystems Applications
Table 2
Table 3
Table 4
Table 5
Table 6
Table 7
Table 8
Table 9 Message
Queue

Log Service
Log Write
Log Read
Log Database Current DB View Association
Previous DB View Association
Logging in OutSystems
Thank You!