application logging

would like to know about the logging facilities provided by agile platform service. I know about "Audit" which is used to presented information in Service Center in the eSpace general log, in production "Audit" will be disabled so it is not the correct option and also "Asynchronous Custom Log" which will log using message queue, still need to use the "Audit" action for logging information.

Need to store the application related information even when the "Audit" is disabled.

By default, the log is stored in Database, is there a way to log the information to files in addition to DB?

Md Ghouse G.

Any update on logging supported by Outsystems.
Hi Md,

In the projects that i've worked we always created an AuditEvents OML, with own DB Tables and public action to create the new record.

With this approach you can have fully costumized audit tool.

Hope that helps!


Let me add two remarks:
  1. 'Audits' are disabled by default in production, however they can be enabled per eSpace in ServiceCenter (go to the eSpace details > Operation tab > Auditing. Not sure if you need to re-publish the eSpace in order to changes to take effect (SC will warn you if so).
  2. Check out the Custom Log technical document for an alternative providing a «highly scalable way to insert data in an asynchronous fashion, allowing for high scalability and maximizing database performance».

Hi Paulo,

Thanks for Reply. am working on JEE environment. As per document "Custom Log" is available in .Net platform only. 

You're right, this was only available for .Net installations.
The good news is that, if you're using version 8, you can use the new Asynchronous Logging API, available in both .Net and Java stacks.

Tip: Although it's not hinted in the online help topic, you can get the LogRecord action from the (system component) AsynchronousLogging extension (Add/Remove References...).
Hi Paulo,

Thanks for the information. Is there a way to log the messages to files instead of DB?

Md Ghouse G
Since the platform is designed to scale horizontally by adding farm nodes, all built-in logging is designed to write to a central repository, the database in this case.

If you want logging to files then you will need to do it on an extension.

In Jboss, both slf4j and log4j are already present and configured to write in the server.log file.
If you choose any of those, please don't include the .jars in the extension or you will have version conflicts.