OEM Monitoring problem with parent tenant app analyzer

[CedricD]

Hi all,

We are currently trying to implement the Qlik monitoring apps into our multi-tenant OEM environment. However, after refreshing a child tenant the OEM app analyzer gives us an error message:

"Unexpected token: '-' expected one of: '.', ',', 'as', 'from', 'into'

Mostly the error is within:
Store consumption >>>>>>-<<<<<<20 into lib/qlikmetacollection/compiledtenants

Ocassionally the error is within:
Store ExportFromApp>>>>>>-<<<<<<20 Into lib/qlikmetacollection/compiledtenants

We have noticed that refreshing the child tenants a few times usually fixes the issue. However, we don't consider this a fix as this is very time consuming to do. Is there anybody that might have an idea about what's going on?

Some additional information:
- We are using all the latest versions of the monitoring apps found on GitHub - qlik-oss/qlik-cloud-monitoring-apps: The Qlik Cloud monitoring apps are a set of community-...
- We have not changed any settings, except the settings that are required to setup the multitenant support, and to specifiy the childs / parent.
- For the parent storage location, we are using Azure Blob.

Thank you in advance

[DaveChannon]

@CedricD our guess is you have mismatched versions generating the QVDs. 

Can you confirm that:

1. All versions of apps are up to date
2. If not, does it work if you delete the compiled QVDs and allow them to be regenerated?

An improvement we will consider is creating a new version of QVDs for each new release to reduce the risk of this happening on upgrades.

[CedricD]

Hi DaveChannon,

Thank you for your response.

To address your questions:

1. Initially, some issues did stem from mismatched versions. However, I have since replaced all the monitoring apps with the latest versions downloaded directly from GitHub. Before upgrading, we ensured a clean slate by deleting all old QVDs, apps, and clearing the Azure Blob.

2. We did delete the compiled QVDs at the start after upgrading to the latest versions, but unfortunately, this didn't fully resolve the issue. During the installation of the apps on each tenant, I encountered the same error repeatedly. Interestingly, after refreshing the monitoring apps a few times, the error disappeared.

For context, here’s a snapshot from our parent OEM monitoring app analyzer history from last night:

• 19 Aug 21:24: Last manual refresh to test all 25 tenants—everything was working correctly. Since then, the system has been reloading on an hourly schedule and has been mostly been succesfull.
  
  And to clarify, we haven't added or changed any child or parent monitoring app since 19 Aug 21:24, so the error has just been popping up again without any apparent reason.

The current reload schedule is as follows:

• 00:00: Hourly refresh of the child apps
• 00:35: Hourly refresh of the OEM apps
• 00:50: Hourly refresh of the OEM dashboard

Our biggest challenge is the inconsistency. Yesterday, I manually enabled all 25 tenants one by one, verifying each for functionality. Once all 25 were up and running, I enabled the scheduled reload. While it mostly worked, we've started encountering errors again since this morning.

I hope this gives you a clearer picture of what's actually going on.

[CedricD]

Hi,

I'm brainstorming here because we are still encountering errors with Sheet consumption. Weirdly enough I was able to do 1 manually reload succesfully, but the automatic and manually reloads afterwards were failing again, while I didn't change / do anything.

Furthermore, I have noticed that the child app_analyzer "sheet consumption.qvd" are not always being generated in the Qlik environment but are still being stored in the Blob. It seems that some "sheet consumption.qvd" are getting stored as an empty file to the blob. Could this be the culprit?

Thank you kindly,