Identify incoming performance log events as coming from either user activities, or other work done in QS

[mountaindude]

Overview

With the implementation of #320 Butler SOS can capture very detailed performance metrics on apps and parts of apps.

Qlik Sense will send (lots of) performance events from the QixPerformance.Engine.Engine module, both during scheduled app reloads and when end users interact with Sense apps.

Goal

The goal of this ticket is to

• Determine if a performance log event relates to end-user and other types of activities
• Store this in InfluxDB together with the log event data
  • Add a new InfluxDB tag called event_activity_source to store this categorisation
  • Store this also for rejected log events, for which only an event count is (optionally) kept

How to identify user activity

The proxy_session_id field contains a GUID if the performance log events originated as a result of user activity (opening an app, making a selection in an app, rendering a chart on a sheet etc).
That field is empty if the event originated from a non-user activity, for example a scheduled app reload.