Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik and ServiceNow Partner to Bring Trusted Enterprise Context into AI-Powered Workflows. Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
adam_b_14
Contributor
Contributor

Qlik Sense Reloads Monitor "missing" Data

Hi,

Strange one, recently started at a new organization and been reviewing Monitoring Apps, I have noticed the 'Reloads Monitor' is missing data at certain points throughout the day.

Which is strange because

- Reloads Monitor is triggered to reload every hour
- There have been no errors on the reload tasks

It is using an Incremental reload on the existing QVD so could be something in that, however never had an issue with this at a previous organization.

Essentially, if I open the 'Reload Summary' sheet and review any app reloads at any time between 3am & 3pm there is no completed reloads showing for that time period, but all history is showing (prior to 3am)

There should at least be completed reloads for the 'Reloads Monitor' due to the fact it's reloading every hour as mentioned above and there are plenty of other apps reloading during this time.

AFTER the reload task that runs at 3pm completes, all reloads for the period above come through and show under completed reloads.

NOTE: The reload that runs at 3pm is the same hourly scheduled Task running throughout the day.

Has anyone else seen this issue or any tips on where the issue might be? 

Thanks,

Adam.

Labels (1)
2 Replies
Vegar
MVP
MVP

Qlik Sense on Windows have two locations for storing log files.

  • In the nodes ProgramData folder
  • In the QlikShare ArchivedLogs folder.

During operation Qlik stores the logs on the node(s), then on a certain schedule or if a size threshold of the local log file has been med the log file get moved into the central ArchivedLogs location.

It could be that the reload monitor application is fetching the parts you are missing solely from the central Archieved Logs and therefore you experience a gap in the details for certain periods.

 

RafaelBarrios
Partner - Specialist
Partner - Specialist

Hi @adam_b_14 

I will bet that your environment is multinode, and the task is ignoring the logs on the rim nodes until they are flushed to archived logs

Check node list in the QMC

RafaelBarrios_0-1777736277138.png

if so, check your script

RafaelBarrios_1-1777736312159.png

 

hope this helps.

Best,

help users find answers! Don't forget to mark a solution that worked for you & to smash the like button!