Hi @HI6,
1- Set-up Notifications for Engine Node Failures:
Qlik Sense Management Console (QMC) Alerts: Use the QMC to configure alerts that can notify you when a node goes offline or encounters issues. While QMC does not directly support notification emails for node failures, you can use third-party monitoring tools integrated with Qlik APIs to trigger emails or messages.
Third-Party Monitoring Tools: You can use systems like Nagios, Zabbix, or Microsoft SCOM, which can monitor your Qlik Sense services and send alerts through email or SMS when a service goes down. These tools can be configured to check the service status via the Qlik Sense Repository Service API and trigger alerts accordingly
2- Enhancing System Redundancy:
Node Redundancy: Ensure that you have multiple engine nodes in your Qlik Sense deployment. This setup enhances fault tolerance by allowing other nodes to take over the workload if one node fails, ensuring minimal disruption to the end users.
Load Balancing: Implement load balancing across your engine nodes to distribute the user sessions and workload evenly. This not only optimizes resource utilization but also reduces the chances of overload on a single node, which can be a cause of failure.
3-Investigating the Cause of Node Failures:
Log Files: Qlik Sense keeps detailed logs that can help you diagnose the reasons behind a node failure. Check the logs located in the folder C:\ProgramData\Qlik\Sense\Log or the corresponding directory if your installation path differs. The logs to look particularly into are:
Engine logs (Engine\Trace): Provides information on the actions performed by the engine and records errors that occur during execution.
System logs (System\Repository\Trace): Useful for understanding the interactions between nodes and the Repository.
** When applicable please mark the correct/appropriate replies as "solution". Please LIKE threads if the provided solution is helpful to. **
.png){kind=link}