What Events are Logged on the Brinqa Platform?

In Application Event Logs, Brinqa stores the record of varying events that have occurred in your instance. For example, when a user logs in or out of the instance, when a data integration sync starts, or if a computation on a dataset finishes without any error. You can use the application event logs to troubleshoot any errors you may come across in your instance.

note

To prevent the logs from filling up the disk, Brinqa launches a cron job to remove old logs. By default, this job runs everyday at 2:00 AM UTC and removes logs older than 30 days. An event is generated when the job finishes, summarizing the number of logs removed and the number remaining.

If needed, you can change the retention period to a number between 7 and 365 (days).

The following table details the default events being logged on the Brinqa Platform:

Category	Events being logged
Audit	Application event log cleanup job completed Config item created Config item updated Config item deleted dataset deleted Inactive data model removal flow launch Inactive data model removal flow cancel Risk factor support enabled on a data model Risk factor support disabled on a data model Role created Role updated SLA support enabled on a data model SLA support disabled on a data model Ticket created Ticket updated User created User updated
Automation	A flow was launched that uses a deprecated flow action A sub-flow execution was skipped because it's inactive Flow execution start Flow execution end - success Flow execution end - failure Flow execution end - cancel Inactive data model deleted successfully Inactive data model deletion start Inactive data model deletion abort, as data model is active Inactive data model deletion error Inactive data model's datasets deletion success Inactive data model's datasets deletion error Rule action execution start Rule action execution end - success Rule action execution end - failure Rule execution start Rule execution end - success Rule execution end - failure
Computation	Computation start (includes which event triggers the computation) Computation end (includes which event triggers the computation) Computation failure (includes reason of the failure and the stack trace)
Export	Export failure
Integration	Data integration activated Data integration deactivated Data integration disconnected Data integration reconnected Data Integration push start Data integration push end Data integration push, external UID not found Data integration push, source not found Data integration push, source UID found Data integration push, creation failure Data integration push, update failure Data integration push, retry Data integration push, successful deletion Data integration push, failed deletion Data integration sync start Data integration sync end - success Data integration sync end - failure Data integration object sync start Data integration object sync end - success Data integration object sync end - failure Data mapping sync start Data mapping sync end - success Data mapping sync end - cancel Data mapping sync end - failure Data source sync start Data source sync end - success Data source sync end - failure
Remediation	Ticket creation failure
Security	Successful log in Successful log out Login failure - wrong credentials Login failure - user is locked out Login failure - forbidden access Request with invalid authentication token Password change request Password change - success Password change - failure Password reset failure
View	A view uses an invalid manifest A view uses an older version manifest and needs to be updated

Footnotes

• Some processes, such as a data integration sync, generate many events for the Audit category. Logging all audit events negatively impacts system performance and should not be done without coordination with Brinqa Support.
• The Rules and Action categories in previous versions have been combined into the Automation category.
• The stack trace in the Computation category displays the name of the user defined library (UDL) in a user-friendly format: script_udl_{name-of-the-UDL}.
• The data integration object in the Integration category represents the objects that Brinqa connectors retrieve from the different data sources.