Skip to main content

Application Event Logs

This article details the application event logs in your Brinqa Platform, how to view and interpret the logs, and how to modify the frequency of purging the event logs.


Application event log is a record of varying events that occur in your Brinqa Platform. For example, when a user logs in or out of the instance, when a flow in a data orchestration executes and if it was successful or failed, or if a calculation of a dataset finishes without any error. You can use the application event log to troubleshoot any errors you may come across in your instance.

To view your application event logs, navigate to Administration administration icon on the upper-right corner and under System, click Logs. The following table details the main elements of the application event log page:

TransactionDisplays a 36-character string with a mix of numbers and letters. You can copy and paste the Transaction ID from a different page into the Application Event Log search bar to locate the specific event you are attempting to locate or troubleshoot. Click the transaction to view details of the record in the event log.
OutcomeThe outcome of the event. Outcomes include: Cancel, Failure, Not applicable, or Success.
UserThe user who originates the event.
CategoryThe category of the event. Categories include: Audit, Automation, Computation, Integration, Security, or View.
SeverityThe severity of the event log. Severity levels include: Error, Info (short for information), or Warning.
  • Error: Indicates when an action or event does not function properly and results in a failed outcome. For example, a failed flow in an automation or an error in calculating a risk score.
  • Info: Indicates a properly executed event with no errors. For example, a flow in a data orchestration completed successfully or a successfully created new user account.
  • Warning: Indicates an issue that disrupts a process but does not necessarily result in a failed outcome. For example, a user canceling a data integration during sync or entering an invalid name for a new data model.
MessageThe summary of the event.
Date timeWhen the event occurs in the instance.

Modify the application event log settings

By default, application events logs are purged after 35 days. If a high number of records in your application event log causes slowdown or instability in your instance, you may want to purge the logs sooner. On the other hand, you may be required to keep your logs for more than 35 days due to compliance. In any case, you can change the frequency of which the application event logs are purged. To do so, follow these steps:

  1. Navigate to Administration > System > Logs.

  2. Click Settings settings icon.

  3. Under Application event logs settings, click the days option. A pane appears.

  4. Enter the number of days which you want to purge the records in the application event log. The default setting is after 35 days.

  5. Click Update and then click Close.