What is logging?
Logging of metric, resource and status information is one of the most important features of FusionReactor. The list of metrics collected has been selected to provide a wealth of information about your application and server environment. Although so much metric information is made available, the 'overhead' of capturing this instrumentation is maintained as an absolute minimum. FusionReactor also provides sophisticated log management, so make sure that you have easy access to the log information and that you're only storing the information you really need.
What are you able to do with the log data?
Armed with the information stored in FusionReactor's logs you will be able to perform:
- Problem solving
- Troubleshooting technical issues, such as poor request performance, crashing servers, Denial of Service (DoS) attacks etc.
- Root cause analysis, which is usually only possible by establishing the sequence of events which have been captured within the logs.
- Business intelligence
- Trend analysis
- All forms of forensic analysis
- Pro-active planning, such as:
- Resource capacity planning for CPU and memory
- Scalability analysis
- Deployment analysis
- Performance tuning and quality improvements, in the form of
- Database usage analysis
- Request performance analysis
- Continuous system/application analysis to measure the performance of your systems on a daily basis, using the following reports which are available in FusionAnalytics
- Traffic, Availability and Performance (TAP) Report
- Daily Status Report
What information is being logged?
This table provides an overview of some of the most important log files which are generated from FusionReactor – Many more log files exist, click here for a complete list.
| Log Name | Description |
|---|---|
Request.log |
Contains a comprehensive set of instrumentation relating to each request executed, such as the Request ID, date/time (ms) when the request was started/finished, request status, thread ID, method etc. |
Resource.log |
Contains information relating to instance and system memory, instance and system CPU, various request count information e.g. total request made (since server restart), finished and queued requests etc. |
Jdbc.log |
All relevant information relating to each DB request, including the full query string, DB start/stop times, query time, DB time, number of rows returned, datasource ID etc. |
Crashprotection.log |
All relevant information relating to the crash protection event, including date, time, CP event which occurred, CP action performed, resource values at point of event etc. |
