After upgrade Log Monitor & other Monitor apps needs 5-6 hours timeout to load successfully

HaseebIqbal — Thu, 11 Jul 2024 02:55:50 GMT

Just notices after upgrading to February 2024 (P5), the monitor apps need larger time (6-8 hours) to complete successfully. After successful for the first time, normally takes less than an hour to complete.

And failing of these apps creates 300-700MB+ script logs every time these fails.

Is it normal? Are we missing anything? Or any expectation been overlooked?

Re: After upgrade Log Monitor & other Monitor apps needs 5-6 hours timeout to load successfully

Alan_Slaughter — Wed, 05 Feb 2025 16:58:57 GMT

Monitoring apps runtime depends on the amount of logs, nodes, and your engine performance.

If you have a large amount of logs it is normal for it to run longer.

You can move logs if they are no longer required.

https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-Enterprirse-on-Windows-Log-Archiver-Eraser/ta-p/1491448

Ensure you do not have a debugging level enabled on your services.

https://help.qlik.com/en-US/sense-admin/November2024/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/Server-Logging-Configuration.htm

topic Re: After upgrade Log Monitor & other Monitor apps needs 5-6 hours timeout to load successfully in Management & Governance

After upgrade Log Monitor & other Monitor apps needs 5-6 hours timeout to load successfully

Re: After upgrade Log Monitor & other Monitor apps needs 5-6 hours timeout to load successfully