Configuring Monitoring Apps in Qlik SenseArticle Number: 000056731 | Last Modified: 2018/09/21
- What are the Monitoring Apps?
- Configuration in a Single-node environment
- Configuration in a Multi-node environment
- Defaults and Limitations
Q: When using logging database, which logs go to database and which to folders?
A: By default, even when using the logging service, all logs files are still written to the normal places.
Only logs from the Engine, Repository, Scheduler, Proxy and Printing Services will be written to the logging database
Q: Does the logging database reduce performance instead of file log?
A: I'm not aware of any performance impact from the logging service in normal circumstances, you may want to ensure that the maximum size is set to a reasonable level however, as the defaults are quite large.
Q: My Montoring apps reload task got failed frequently
A: Unfortunately there are many reasons the monitoring apps can fail to reload https://qliksupport.force.com/articles/000024083 is a comprehensive article if you run through all 30 steps then almost all problems that prevent the monitoring apps from reloading properly will be fixed.
Q: How to install Log, Session, Reloads monitoring apps?
A: These are found in C:\Program Data\Qlik\Sense\Repository\Default Apps\ and can be imported like any other qvf
Q: Can QlikSense installed on a non OS drive? If yes it still does wrires back to OS drive. Can this be changes back to Application drive?
A: Yes Qlik Sense can be installed on a non-OS drive, however it will write a lot of data to %programdata% which is normally located on C:\.
Q: Sometimes the environment (Hub or QMC) is not available although all windows services are running. Is there any way to run any healthcheck in real time?
A: If you are unable to access the hub or QMC then the monitoring apps will be unable to help you, you should manually check the log files to find out any errors. The Qlik Sense Log Collector and Qlik Cockpit are both available in your Qlik Sense install folder to help in this situation.
Q: Is it possible to be alerted about certain failures? For example, Hub is not available, a node/proxy/virtual proxy/repository is not running etc. (these states are present in QMC)?
A: Unfortunately there is no built-in function for this, you could monitor if the apps are listening to certain API calls and then build your own monitoring service for this.
Q: Is there a way to include information regarding the reloads that users are starting during development? Sometimes users will start long running or cartesian product tasks, however admins are unable to identify the applications which are causing issues
A: I'm not sure if there is a way to do that in the monitoring apps as they currently exist, I will pass that feedback along to the team that works on them however.
Q: Given the delay of the data refresh - what is a common best practice around aggregating and then monitoring the data from a real time context - example : production node is part of the "production monitoring dashboard" which is rendered via something like Elastic Search & Kibana or such
A: I'm not aware of any common solutions for this problem, though certainly something could be built along these lines.
Q: Did you say that the Qlik Service Account need a license/token to be able to run the apps monitor ? Am I wrong ?
A: The exact opposite, you should not assign a license or token to the Qlik Service Account, as if you attempt to use it to access the hub it will often be out of sessions and give you an error.
Q: Is there a detailed guide available to reference all these steps you have talked about?
A: There is the recording of this seminar as well as https://help.qlik.com/en-US/sense/September2018/Subsystems/Monitoring/Content/Sense_Monitoring/Introduction/Configure-monitoring-apps.htm, when November releases these instructions will be updated to fit the same format as I discussed in this seminar
Q: In addition to rest connections with name "monitoring..." I have set of others with name "QS_..., for example "qrs_aap". Are they related to monitoring apps? Are they obsolete?
A: Those may be the older connections that were used in earlier versions of the Qlik Sense Monitoring Apps. I would check to see if anyone is using them before removing them however.
Q: Shouldn't the monitor app be scheduled 1 once day because it does comsumes resources and we noticed it has casused issues in the pass with other reloads?
A: We default to once an hour, it depends on the size and power of the systems involved, it is relatively uncommon for them to take significant resources to reload, most of the time that has occurred the best approach is to delete the existing QVDs and reload the apps.
Q: If you make updates to the monitoring apps per multi node (to loop through logs on multiple rim nodes for example), do those changes get reverted when you upgrade versions of QlikSense?
A: Yes, the new versions of the monitoring apps will need to have their script altered to include the connectors for the rim nodes.
Q: One short question, where can i change the schedule from the task?
A: In the task interface, double click on the task to edit the schedule.
Q: For each release, do the apps themselves need to be updated to support multi-node environments?
A: If you are using the log files then yes, they will unfortunately need to be updated every release.
Q: Do updated versions of the monitoring apps get deployed when you update qliksense version?¬
Q: Some times, if we connect the Rest connector to get the data after run the job we are gettingt the error like Error: QVX_UNEXPECTED_END_OF_DATA: HTTP protocol error 503 (Service Unavailable):
A: https://qliksupport.force.com/articles/000024083 should cover the steps for fixing those kinds of errors
Have a Question?
Search Qlik's Support Knowledge database or request assisted support for highly complex issues.Submit a case
Experiencing a serious issue, please contact us by phone. View phone numbers and hours by region.