|
If you encounter an issue, and want to report it to Sentry Software, you will be asked to enable the Debug Mode and provide the debug output to the Sentry Software support team. The debug output file will allow you to:
| • | have debug information about the discovery process since debug information about the discovery process may be lost by the PATROL Console during the PATROL Agent startup. |
| • | trace the activity of Monitoring Studio for a few minutes since information may also be lost by the PATROL Console if its buffer is full. |
To enable the debug mode
| 1. | Right-click the main Monitoring Studio icon > KM Commands > KM Settings > Debug... |
Enabling Debug Mode
| 2. | Check the Enable Debug Mode option. |
| 3. | Indicate the date and time at which the system must stop logging debug information. The required format is: YYYY/mm/dd HH:MM:SS, based on a 24 hour-day. |
| 4. | Click OK. The debug files will automatically be saved in the %PATROL_HOME%\log or $PATROL_HOME/log folder. |
 The following debug files are generated:
| ▪ | SEN_MS_debug_km_<PatrolAgent_Port>_<YYYY-mm-dd-HH-MM>.log, with the debug output of the KM (example: SEN_MS_debug_km_3181_2016-02-12-17-25.log) |
| ▪ | SEN_MS_CollectionHub_debug_psl_<PatrolAgent_Port>_<YYYY-mm-dd-HH-MM>.log, with the PSL debug output of the Collection Hub (example: SEN_MS_CollectionHub_debug_psl_3181_2016-01-27-09-27.log) |
| ▪ | SEN_MS_CollectionHub_debug_java_<PatrolAgent_Port>_<YYYY-mm-dd-HH-MM>.log, with the Java debug output of the Collection Hub (example: SEN_MS_CollectionHub_debug_java_3181_2016-01-27-09-27.log) |
|
