"Restoring Monitoring logging" in Monitoring & Diagnostics page does not work to disable monitoring logging of TIBCO Spotfire Web Player
Article ID: KB0079753
Updated On:
| Products | Versions |
|---|---|
| Spotfire Server | 7.12, 7.13, 7.14, 10.0 |
Description
The logging level of the TIBCO Spotfire Web Player can be increased when investigating issues by using the "Enable Monitoring Logging" option on the Monitoring & Diagnostics page. See the reference Logging and exporting monitoring diagnostics for more details. This will increase the logging level to DEBUG until the service is restarted or manually change. To restore the logging levels to what is specified in the log4net.config file, you can use the "Restoring Monitoring Logging" option.
In versions 7.12, 7.13, 7.14, and 10.0, when "Restoring Monitoring Logging" is selected to switch back the logging configuration, the monitoring logging status on the Instances tab does not switch back to "Monitoring logging (Currently off)" and instead remains set to "Monitoring logging (Currently on)", as seen here:
In versions 7.12, 7.13, 7.14, and 10.0, when "Restoring Monitoring Logging" is selected to switch back the logging configuration, the monitoring logging status on the Instances tab does not switch back to "Monitoring logging (Currently off)" and instead remains set to "Monitoring logging (Currently on)", as seen here:
Issue/Introduction
This article will give you information about the defect that is identified in TIBCO Spotfire Web Player 7.12, 7.13, 7.14, and 10.0.
Resolution
This is due to a defect in TIBCO Spotfire 7.12, 7.13, 7.14, and 10.0.
If the logging level does not get restored back to INFO level as expected, you can restart the Web Player instance so that the logging level is restored to the level defined in the log4net.config. This can be done on the Nodes & Services page by selecting the Web Player instance and clicking the "Restart" button.
If the logging level does not get restored back to INFO level as expected after Web Player instance restart, you may need to verify the logging level set in the log4net.config to ensure that does not have the enhanced DEBUG logging level set. In that case, the DEBUG, monitoring logging level is the default expected logging level for that instance. See the reference Customizing the service logging configuration for more details.
If the logging level does not get restored back to INFO level as expected, you can restart the Web Player instance so that the logging level is restored to the level defined in the log4net.config. This can be done on the Nodes & Services page by selecting the Web Player instance and clicking the "Restart" button.
If the logging level does not get restored back to INFO level as expected after Web Player instance restart, you may need to verify the logging level set in the log4net.config to ensure that does not have the enhanced DEBUG logging level set. In that case, the DEBUG, monitoring logging level is the default expected logging level for that instance. See the reference Customizing the service logging configuration for more details.
Additional Information
Doc: Logging and exporting monitoring diagnostics
Doc: Customizing the service logging configuration
Feedback
Yes
No
Powered by
