Document Actions
Log Files
Overview
Two kinds of log files are used in the Mifos system, Change Logs and Application Logs. Change logs capture and store information on all the activities performed on data. Application log consists of error messages, warnings, and actions performed by the users of the system.
The following sections describe the functionality of the log files.
Change Logs
The change log is required to capture the instance of creation and modification of data in the system so that this information can be used for future reference. The data management pages in the system have options for viewing change log data.
- The system records details of data creation/modification like, who created or modified the data and when.
- It records the old and new value of the data modified.
Functionality
Change logs are captured in each installation of Mifos.
- Change Log captures the following details:
- Change made by or Record created by (User Name of the user will be recorded)
- Date of change of record
- Field that was changed
- Original data value
- Modified data value
- Change logs are captured for the following entities:
- Clients
- Groups
- Centers
- Loan Accounts
- Savings Accounts
- Personnel
- Loan Product details
- Savings Product details
- In v1.1 the following changes will always be captured and can be relied upon:
- Status changes for clients, groups, centers, loan accounts, and savings accounts
- Loan officer changes for clients, groups, and centers
- Additional data changes will be recorded in the change log, but there is no guarantee in v1.1 that any change, other than the status and loan officer changes listed above, will be captured in the change log.
- Activities for which the change log captures data changes are pre-configured in Mifos. New activities cannot be brought under the scope of the change log.
- Change log for a particular entity would be visible from the section where details of the entity are created or modified. The change log is accessible through a link off each page. The data is in a flat list format organized by date.
Out of Scope for Version 1.0
- Ability to select changes to “reverse-out”
- Facility to configure which data changes need to be logged
- Export and print of the change log entries
- Financial transactions in the change log
- Archival of change logs
Application Logs
Application log comprises of debug or error messages, warnings, and actions by the users. A severity or importance level is assigned to all entries in the application log. The entries can be sorted by the severity levels, thereby enabling users to focus on issues of interest. System administrators are able to turn off and on certain types of logging by setting a configuration value.
The application log is stored on the server; it serves a surveillance function over the application.
Functionality
Application logging is enabled at the module level, and hence there are different loggers per module. This is done so that various modules can have different levels of logging. The stabilized modules log only 'ERROR' or 'FATAL' levels. while the modules under development would be at 'DEBUG' level. Modules that are released and are relatively, but not completely, stabilized are logged at 'INFO' level.
Developers can use application logging to identify where a particular error has occurred as well as test proper functioning.
Out of Scope for Version 1.0 and Version 1.1
- Functionality to define new instance for the creation of application logs
- Option to configure features to be logged
- Analysis and reporting on the log information stored in the database or files
- Export or print the logs
- UI for viewing the application logs
#000000