Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Qlik Sense June 2018 v12.26.1
Monitoring Apps v7.10.0
Background: Upgraded to QS June 2018 in September. In reviewing Operations Monitor, we noticed a massive decrease in session counts for Nov 2018 - see pictures below. Any suggestions on where to start troubleshooting? We have added users and published more applications, so the drastic decrease is puzzling. Thanks in advance for any and all constructive advice.
I wanted to update the thread as to the cause of our issue - see attachment. On install, the schedule's timezone was set for 0000 UTC, which does not recognize daylight savings time. On 4 Nov 18, time changed. The result was that any access, of an application, that was less than one minute, had its' start time greater than its' end time and was excluded from the analysis. Once we changed the timezone to 0600 Central Time, the issue went away - going forward. Still have not modified the historical data. Hope this helps someone else.
Hello,
Are you using the Qlik Logging Database?
The first thing you could try to do is to force the monitoring app to load its data from the log files and not from the database.
To do that please follow the below steps:
If it still does not work, you might want to take a look at the script logs and compare them to a date it was working fine to see where is the difference.
Hope this helps,
Kind regards,
Thank you for the insight. I will try this next week, after the holidays, and report back.
Same results. Looks like I will have to dig through the script logs. Thank you for the tip.
I wanted to update the thread as to the cause of our issue - see attachment. On install, the schedule's timezone was set for 0000 UTC, which does not recognize daylight savings time. On 4 Nov 18, time changed. The result was that any access, of an application, that was less than one minute, had its' start time greater than its' end time and was excluded from the analysis. Once we changed the timezone to 0600 Central Time, the issue went away - going forward. Still have not modified the historical data. Hope this helps someone else.
You mentioned that "you had not modified the historical data" - did you later attempt this?