In some situations, it is possible for an application owner or Administrator to trigger very large numbers of long-running calculation jobs.
Audit Logging is enabled which captures every detail about everything every user does but it may not be clear how to find the information in the audit log data that are related to the event that caused the creation of calculation jobs.
Audit Logging must be enabled and functioning on the Archer instance BEFORE the jobs are created.
The audit logging will capture the event of a recalculation that is triggered in the Application Builder.
The syslog server needs to be queried for the event data. The process to query the syslog server will vary depending on what capabilities/features/software is being used on the syslog server.
Below is an example of the audit logging message that gets sent to the configured Audit Logging (syslog) server when any user clicks the recalculate button from the application builder:
The eventtime highlighted above indicates the date and time the action was triggered by the user.
The "MethodName:ModuleManager.RecalculateLevel" highlighted above is the key event that indicates a level recalculation has been triggered by a user from the Application Builder.
The UserName: "Administrator, System" highlighted above indicates the user that triggered the level recalculation.
The 37 highlighted above indicates the level ID that was triggered for recalculation. This levelID is associated with an application/module. The LevelID is also in the payload (XML) of the Archer level recalculation job.