Operation Monitor not displaying rim node scheduler data in the Task Details sheet

[Bastien_Laugiero]

In multimode environment, after making sure that the Operation Monitor is properly configured following Configure Monitoring Apps , it appears that the task details executed by the rim node are not appearing. In fact they all appear under the central node. 

The Reload Monitor however works as expected. 

Environment

• Qlik Sense Enterprise on Windows (Any Version up to November 2020 at least)

Resolution

Below are the changes required in the Operation Monitor to extract the correct host from the scheduler's AuditActivity log itself so that the filter on rim node in the Task Details sheet should now show the reload summary statistics chart for those tasks instead of being blank.
However, these charts should be used only for summary, and if the detail level task execution
breakdown is needed you should look it up in the reloads monitor as that uses the TaskExecuton trace
logs for its purposes which contains much more granular details.

Step by step instruction:

• Duplicate the Operation Monitor (from the Hub or QMC)
• Open the duplicated version and go to Data Load Editor
• Go to the “defineFields” section
• Replace in that section

lower(Hostname) as Hostname

by

Lower(If(Left(Message, 12)='&chr(39)&'Sending task'&chr(39)&', Subfield(Subfield(Message, '&chr(39)&' '&chr(39)&', -4), chr(46),1), Hostname)) as Hostname

Note: (This portion is present in 4 different variables in the “defineFields” section. All 4 variables needs to
be updated)

• “Publish” or “Publish and Replace” the updated Operation Monitor and run a reload from the
  QMC

The changes above will be released in a later version of Qlik Sense. 

Information provided on this defect is given as is at the time of documenting. For up to date information, please review the most recent Release Notes, or contact support at support.qlik.com with the ID QB-2978 for reference.

Cause

Product Defect ID:  QB-2978

The Operations Monitor being a generalized summary app, it does a lot of things but doesn't go into
granular details for each.
It only loads 3 Trace logs (Engine\Performance, Engine\Session and Repo\Synchronization), as trace logs
are generally heavy especially for execution results.
The Reloads monitor uses the Scheduler\TaskExecuton Trace logs for its purposes, which we don't use in
Operation Monitor.

The ExecutingNodeName field used in Reloads monitor is sourced from Scheduler\Trace\TaskExecution
logs which is not loaded by Operation Monitor and this explains the difference between the two apps.