Monitoring Apps - any interdependencies

Ken_T — Sun, 12 Feb 2023 19:55:47 GMT

There are a handful of Monitoring apps provided with the qlik enterprise system.

App Metadata Analyzer
Connector Logs Analyzer
License Monitor
Log Monitor
Operations Monitor
Reloads Monitor
Sessions Monitor

Do these have any interdependencies?
Meaning, can one be fully reloaded (start over from scratch) without affecting the others?

Is there any order that they should be initially set up, or can they all be running a reload for all of them at the same time?
Example Should the Operations Monitor be up and loading before Sessions Monitor is set up and loading?

Do any of these qlik-provided apps use and share any common data files that the monitoring apps create (qvds, txt files etc) ? another form of interdependency

is there any documentation about the interdependencies anywhere?

Re: Monitoring Apps - any interdependencies

Chip_Matejowsky — Mon, 13 Feb 2023 13:32:54 GMT

Hello @Ken_T,

The Qlik Sense Online Help entries for the Monitoring Apps doesn't list any interdependencies:

I believe the only caveat to consider is the below snippet from the Sessions Monitor entry:
Sessions Monitor uses the ProxySessionId from the engine's session logs for deriving its session counts like Operations Monitor, which effectively gives the proxy session counts. Sessions Monitor also registers short sessions (less than 40 seconds) that are excluded in the Operations Monitor due to their respective design choices. Therefore, the Sessions Monitor session counts can sometimes lie in between the session counts of Operations Monitor and License Monitor.

The Qlik Sense Admin Playbook also has some helpful information regarding the monitoring apps under the Tooling Appendix.

Best Regards

topic Re: Monitoring Apps - any interdependencies in Management & Governance

Monitoring Apps - any interdependencies

Re: Monitoring Apps - any interdependencies