Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
Tanalex
Creator II
Creator II

Operations Monitor "Losing" Data

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.

UserAppCountTrend.png

Nov2018.pngOct2018.png

Labels (2)
1 Solution

Accepted Solutions
Tanalex
Creator II
Creator II
Author

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.

 

OPMONIssue.png

View solution in original post

5 Replies
Bastien_Laugiero

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: 

  • Go in the Script Load Editor for the Operation Monitor
  • In the first tab called Initialize, line 10 you should see the following variable db_v_file_override
  • If you set this variable to 1 you will force the monitoring app to load from file
  • Please make sure that in QMC -> DataConnection, the path referred for ArchivedLogsFolder is correct 
  • Finally, you can try to reload the monitoring app to see if you get the expected data. 

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, 

Bastien Laugiero
If a post helps to resolve your issue, please mark the appropriate replies as CORRECT.
Tanalex
Creator II
Creator II
Author

Thank you for the insight.  I will try this next week, after the holidays, and report back.

Tanalex
Creator II
Creator II
Author

Same results.  Looks like I will have to dig through the script logs.  Thank you for the tip.

Tanalex
Creator II
Creator II
Author

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.

 

OPMONIssue.png

ksmith24
Contributor III
Contributor III

You mentioned that "you had not modified the historical data" - did you later attempt this?