STT - Troubleshooting Qlik Sense Engine

[Bjorn_Wedbratt]

This session will address the following:

• Exploring the Qlik Sense Enterprise Engine Service
• Demonstrating Troubleshooting Techniques
• Configuration Best Practices

Related Content:

QIX engine memory and CPU management
How to troubleshoot  Engine related issues 
How to collect log files from Qlik Sense Enterprise on Windows 
Qlik Sense Enterprise on Windows help (Help.com)
Websocket Connectivity Tester 
How to enable Qlik Sense QIX performance and telemetry logging

Q&A - Troubleshooting Qlik Sense Engine

Q: Do you plane make the same event about MultiCloud special QSEfE?
A: Please check out our Techspert Thursday presentation: The Essentials of Qlik Sense Multi-Cloud

Q: Hi, how do we identify whether QlikSense is releasing memory when app timeout occurs.
A: Please check out the Telemetry links below

Q: When does memory allocated by cached result sets return to 0 or close to 0?
A: Only when you restart the service

Q: Can you talk again about the engine being "attached" to the virtual proxy. What does this mean, what are we confirming? I missed this.
A: The Virtual Proxy must have an Engine attached in order to process data. The setup for this is in the VP config of QMC

Q: Are there good strategies in troubleshooting outages or QS Engine slowness by looking in the Operations Monitor? 
A: Yes, the Ops Monitor will show you trends over time and you can correlate that to system usage. Keep in mind that the Ops Monitor only pulls from Archived Logs

Q: Are 10000 users to much for QlikSense? Accessing the hub is quit slow.
A: Largely depends on the size of your system, but that's on the high end of what I've seen in the field. Are all users active on the system? If not, I would use an LDAP filter to only include the ones you need. Or use the option to only sync the users that are active.