Difference between revisions of "Logging"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| − | There are a number of ways that the Fusion Metadata Registry logs information | + | There are a number of ways that the Fusion Metadata Registry logs information regarding the requests made to it and what work it is performing. These logs can be long and complicated, but it is important to have an understanding of what the system is doing. |
| − | The actual logs generated are controlled by a system setting in the FMR which directly relates to the logging tool that the FMR uses, which is called Logback. The actual files generated are also affected by the Java Web-Application Server you are running (for example Apache Tomcat). | + | The actual logs generated are controlled by a system setting in the FMR which directly relates to the logging tool that the FMR uses, which is called Logback. The actual files generated are also affected by the Java Web-Application Server you are running (for example Apache Tomcat). There are also log tables within the database which persist some of this information. |
| + | |||
| + | =Logback= | ||
| + | |||
| + | =Tomcat Log files= | ||
| + | |||
| + | =Database Tables= | ||
* Log Tables | * Log Tables | ||
* Audit Tables | * Audit Tables | ||
Revision as of 03:33, 8 December 2023
There are a number of ways that the Fusion Metadata Registry logs information regarding the requests made to it and what work it is performing. These logs can be long and complicated, but it is important to have an understanding of what the system is doing.
The actual logs generated are controlled by a system setting in the FMR which directly relates to the logging tool that the FMR uses, which is called Logback. The actual files generated are also affected by the Java Web-Application Server you are running (for example Apache Tomcat). There are also log tables within the database which persist some of this information.
Logback
Tomcat Log files
Database Tables
- Log Tables
- Audit Tables
