To understand the current state of an environment and monitor problems impacting end-users, OutSystems allows you to:
- See the logs of your web and mobile applications;
- Manage the feedback submitted by end-users;
- See the environment change logs;
- View analytics about the user experience of your applications.
To access the first three options, go to the 'Applications' section in LifeTime and click on the icon ▼ right next to the environment name.
To view analytics about the user experience of your applications, click on the 'Analytics' area.
By clicking 'View Logs' you are redirected to the 'Monitoring' area in the environment management console, which allows access to:
- general and error logs, including log messages from the native mobile app shell;
- invoked web services;
- events logged when executing web and mobile requests;
- executed Timers;
- more useful information to monitor your applications.
Almost all log options allow you to export the logs to Excel, so that members of the operations team can analyze these logs and share them if needed.
This screen presents all errors generated by the platform, either implicitly like system errors or explicitly, such as exceptions raised by an application on its logic. This screen will also present any native app shell log entries with log type
Fatal, containing errors occurred in mobile devices of end users. Security exceptions are also displayed in this screen, such as when an unregistered user tries to access a page.
By clicking the 'Detail' link of the log, it is possible to analyze the execution stack trace.
This screen displays system and application activity, either implicitly like slow query warnings, or explicitly by invoking the 'Audit' System action in the applications. This screen will also list the deployment steps when an application is being deployed, as well as native app shell log entries with log type
It allows you to understand probable causes of slowness in your applications.
Displays each timer that was executed, when the timer was scheduled to run, how much time it took to execute, and when it's scheduled to run again.
This screen allows troubleshooting asynchronous logic that relies on timers for its execution.
- Consumed Web Services
Displays all calls made to a Web Service, information about the application module that invoked the service, and how much time the service provider took to respond.
It allows you troubleshooting errors in your applications due to Web Service calls.
- Exposed Web Services
Displays all incoming Web Service requests, which application module handled the request and how long did it took to reply.
It allows understanding the incoming requests to the environment at any given moment.
- Displays all extensions actions run during a web request, the caller module, and how long did the extension action took to reply.
Displays the time the server took to serve a resource the user was trying to access.
It allows you to understand which screens are taking too long to be delivered to end-users.
Displays all e-mails sent, and if they were successfully delivered or are still pending. When developing your applications, it's also possible to choose if the content of the e-mail is logged or not.
It allows you to troubleshoot application logic to understand if e-mails are being correctly send.
- Process Monitoring
For each business process it displays the number of currently active, suspended and closed instances. It also shows the number of instances with errors.
It's also possible to see if a business process instance has executed successfully or with errors, and suspend or terminate it.
- Environment Health
Displays the status of the services running on each front-end, the status of asynchronous tasks, such as processes, e-mails, and timers. It provides an overview of the status of your environment.
Note: The information about the Scheduler Service in the "Environment Health" screen applies only to applications that are not running in a container.
Native App Shell Logging
OutSystems allows you to have full visibility of all the errors that may be occurring in the devices of end-users of your mobile apps. This capability allows you to understand and act fast on any problems detected in your mobile apps.
The native app shell logs are displayed in the 'Errors' and the 'General' screens. Each log entry contains the OutSystems native plugin that triggered the log message in the "Module" field, while the "Stack" field displays the stack trace of all native components used until reaching the point that triggered the log message.
Native app shell logs contain the following device information:
- The Android/iOS device model (e.g.
- The native platform version (e.g.
- The cordova version used to build the app (e.g.
- The device universal unique identifier (e.g.
- The network connection type (e.g.
- The base version used to generate your application (e.g.
- The network connection status (e.g.
Service Actions Logs
The amount of information in each Service Actions log depends on the Logging Level set for the Module where that Service Action lives.
The following image shows the details of an error log entry, available at
Full Logging Levels.
Service Action logs contain a
Request Key field that can be used to pinpoint the origin of a chain of requests by allowing you to relate all logs from the same top level request.
Learn more about understanding an OutSystems error stack.
Clicking on 'App Feedback' link directs you to the console where you can manage feedback from your business users. It allows you to streamline the feedback gathering process and defect tracking.
Learn more about enable user feedback on applications.
View Change Log
Clicking on 'View Change Log' directs you to the audit logs for that environment.
Learn more about monitor usage with audit logs.