Add counters for incoming events from Qlik Sense

[mountaindude]

Current situation

User and log events arrive in the form of UDP messages, sent by means of log appender XML files on the QS server(s).
The event type is either user or log.

The events have a name field identifying the kind of content the event relates to.
Current user event names are

• qseow-proxy-connection
• qseow-proxy-session

Current log event names are

• qseow-engine
• qseow-proxy
• qseow-repository
• qseow-scheduler
• qseow-qix-perf

If an incorrect log appender is configured and sends UDP messages to Butler SOS, those messages will be rejected with a warning in the Butler SOS console/file log.

Suggested change

To get a better understanding of how how many UDP messages are sent from QS to Butler SOS counters could be added.
There would be separate counters for all event types, and one for unknown/unrecognised event names.

The counters start from zero when Butler SOS is started.

Config file changes

• Enable/disable tracking of rejected events on a global level
• Global, configurable interval for writing rejected events summary to InfluxDB
• Configurable InfluxDB measurement name
• Enable/disable tracking separately for user and log events

Qix performance monitoring

For qseow-qix-perf log event messages there could potentially be very large message volumes.
For example, during reloads there will be a reload progress event every 2 seconds, which will result in large number of events for long running reloads.
As part of #320 Butler SOS will include filtering capabilities that when used will (greatly) reduce the number of datapoints written to InfluxDB.

This means that some log events will be rejected by those filters.
But how many and which ones?
Write a summary of the rejected qseow-qix-perf events to InfluxDB, broken down by the event's method and object_type properties.

In order to avoid putting too much stress on InfluxDB and Butler SOS itself this data would be written to InfluxDB at a configurable interval (something like very 5 minutes).

InfluxDB schema

A new measurement "event_count" would be added, with tags

• event_type: user or log.

• event_name: unknown or the event names listed above

• For logs the following tags will also be used

  • app_id
  • method
  • object_type

It should also be possible to define static tags in the Butler SOS YAML config file.
These tags should be added to all datapoints written to InfluxDB.