Logging
Last updated
Last updated
appRules includes several options for logging entries in the project database and for reporting. Normal Log entries are by default automatically written to the project database by the running process or they can be written to the database by using a logging activity (WriteLogs) at specific points in the running process. Extended or Debug Logs are automatically written to the file system in the appStrategy/PortalData/<Company>/DbFiles/<ProjectDatabase>/Logs folder. (<Company> default is Default for a single company environment). The file name is prefixed by the project name + a timestamp.
You can set the default logging options for your project by setting the LogOption property in the Run Options tab of the Project Details window:
You can also specify the logging option for each activity in your project by setting the LogType property of the activity. The LogType property can be accessed by clicking the Option property button of the Configure Activity page.
Select your logtype option:
None: Only errors will be logged in the database Normal: Logs will be written to the database Debug: Extended logs will be written to a specific file (stored in C:\ProgramData\appStrategy\PortalData\Default\DbFiles\<ProjectDatabaseName>\Logs)
Log entries can be viewed by selecting either the Project Run Details or View Logs option from the Log/Statistics menu option in the main menu.
Or from the Log/Stats button in the project bar for the current opened project.
The Project Run Details shows the run instances and tabs showing the statistics and logs for each run (instance) of the project.
The Log Entries selection allows you to select the list and type of log entries to view.
appRules creates log files for certain errors or processes. For example, if the project database is not available, errors are automatically written to the Logs folder (C:\ProgramData\appStrategy\PortalData\Default\DbFiles\<DataBaseName>\Logs).
When tracking down an issue after running your project, you should first check the project logs as shown in the section above. In addition, you should also check the System Log Files option or Logs folder for any message files that may have been created by the process.
The appRules Portal Application application includes tools that you can use to view Logs and Statistics stored in the project database as you run your jobs. The viewers can be accessed from the “Logs/Statistics” menu or the Logs/Stats button for the current opened project.
You can configure your projects to capture as much information as possible regarding the process. After running the job or while it is still running, you can use the Project Run Details window to view all details related to the job, including Activity statistics, Source and Target statistics and system logs. The Project Run Details gives you a centralized report showing all details about instances of the project.
In addition, the Project Run Details also allows you to view details on child jobs launched by each job.
Database Log Entries captured during the course of running your jobs can be viewed using the Database Log Entries of the Logs/Statistics menu. Log entries can be selected by date range and other criteria.
Each run instance of a project makes an entry in the Run Instance table. This selection shows a summary of the run instances for the project selected by date range.
This selection allows you the view the statistics for each activity for each instance of the project. Entries can be viewed by specifying a date range.
This selection shows statistics on data sources that have been used by projects in the project database. Entries can be viewed by specifying a date range.
