User and Log Events

[MarioShuuya]

Hello,
we wanted to activate the new feature qix performance added with v11.0.0 but are struggling to get any data into our Influx2 DB.

Our butler-sos v11.0.3 is running in k8s with the neccessary ports open, 9996 UDP and 9997 UDP. We tracked with Wireshark if our Qlik Sense February 2024 Patch 4 Version is sending any UDP data and it does. The packages are also received on the butler-sos pod.

It seems as it does not write anything into the Influx DB

2024-10-25T10:28:35.374Z �[32minfo�[39m: USER EVENT: UDP server listening on 0.0.0.0:9997
2024-10-25T10:28:35.375Z �[32minfo�[39m: LOG EVENT: UDP server listening on 0.0.0.0:9996
2024-10-25T10:28:55.345Z �[36mverbose�[39m: EVENT COUNTS: Timer for storing event counts to InfluxDB triggered
2024-10-25T10:28:55.346Z �[34mdebug�[39m: EVENT COUNT INFLUXDB: Log events: []
2024-10-25T10:28:55.346Z �[34mdebug�[39m: EVENT COUNT INFLUXDB: User events: []
2024-10-25T10:28:55.346Z �[34mdebug�[39m: EVENT COUNT INFLUXDB: Wrote data to InfluxDB v2

If you could please support us and tell us where we have a configuration error.
Attached is the log of butler-sos, a screenshot of the available Influx DB fields and our configuration yaml for the deployment.

butler-sos-udp-log.txt
dev-cm.txt

[mountaindude]

I have seen a strange, possibly related thing on a couple of Qlik Sense environments I have worked on recently.

Even though an XML appender file is deployed in the engine folder on the server (you have deployed that XML file, right..?) there are no events flowing from Sense to Butler SOS.
And with no Qix performance events arriving, there of course will not be anything written to the InfluxDB.

At this point I don't know why that is happening.
My best guess is that the engine service has to be restarted for the new XML appender file to be recognised.
That is usually not needed for other Sense services, but maybe the engine service is special in that respect.
Just guessing really..
I have not yet been able to restart the engine services on the Sense environments where I have noticed this, will try to do so sometime up ahead.

On the other hand, the concept works flawlessly on the Sense environments I have tested locally here.
So I am not sure what's going on.

Looking at the config file you provided, it should pick up Qix performance events for all apps, all object types and all methods.
I.e. everything. In a busy Sense environment that would be LOTS of data. Just so you are aware of that.

To test the hypothesis of no events being sent from QS to Butler SOS, you can enable verbose logging in Butler SOS.
Add the command line option --loglevel verbose or set the Butler-SOS.logLevel setting in the config file to verbose.
Don't forget to restart Butler SOS for the change to take effect!

Then open a Sense app.
If things work as intended you will see something like this in the log, indicating that Butler SOS is receiving Qix performance event messages:

2024-10-25T12:53:26.034Z verbose: LOG EVENT: qseow-qix-perf:pro2-win1:INFO, QixPerformance.Engine.Engine, LAB\goran, 5b817efe-472d-43ce-8a31-6cce34af7de9, Global::OpenApp, Object type: <Unknown>
2024-10-25T12:53:26.058Z verbose: LOG EVENT: qseow-qix-perf:pro2-win1:INFO, QixPerformance.Engine.Engine, LAB\goran, 5b817efe-472d-43ce-8a31-6cce34af7de9, Doc::GetAppProperties, Object type: <Unknown>
2024-10-25T12:53:26.111Z verbose: LOG EVENT: qseow-qix-perf:pro2-win1:INFO, QixPerformance.Engine.Engine, LAB\goran, 5b817efe-472d-43ce-8a31-6cce34af7de9, Doc::CreateSessionObject, Object type: <Unknown>
2024-10-25T12:53:26.112Z verbose: LOG EVENT: qseow-qix-perf:pro2-win1:INFO, QixPerformance.Engine.Engine, LAB\goran, 5b817efe-472d-43ce-8a31-6cce34af7de9, Doc::GetAppLayout, Object type: <Unknown>
2024-10-25T12:53:26.133Z verbose: LOG EVENT: qseow-qix-perf:pro2-win1:INFO, QixPerformance.Engine.Engine, LAB\goran, 5b817efe-472d-43ce-8a31-6cce34af7de9, GenericObject::GetLayout, Object type: AppPropsList
2024-10-25T12:53:26.143Z verbose: LOG EVENT: qseow-qix-perf:pro2-win1:INFO, QixPerformance.Engine.Engine, LAB\goran, 5b817efe-472d-43ce-8a31-6cce34af7de9, Global::GetAuthenticatedUser, Object type: <Unknown>
2024-10-25T12:53:26.145Z verbose: LOG EVENT: qseow-qix-perf:pro2-win1:INFO, QixPerformance.Engine.Engine, LAB\goran, 5b817efe-472d-43ce-8a31-6cce34af7de9, Global::GetConfiguration, Object type: <Unknown>
2024-10-25T12:53:26.159Z verbose: LOG EVENT: qseow-qix-perf:pro2-win1:INFO, QixPerformance.Engine.Engine, LAB\goran, 5b817efe-472d-43ce-8a31-6cce34af7de9, Global::GetConfiguration, Object type: <Unknown>
2024-10-25T12:53:26.160Z verbose: LOG EVENT: qseow-qix-perf:pro2-win1:INFO, QixPerformance.Engine.Engine, LAB\goran, 5b817efe-472d-43ce-8a31-6cce34af7de9, Global::GetConfiguration, Object type: <Unknown>
2024-10-25T12:53:26.176Z verbose: LOG EVENT: qseow-qix-perf:pro2-win1:INFO, QixPerformance.Engine.Engine, LAB\goran, 5b817efe-472d-43ce-8a31-6cce34af7de9, Doc::GetObject, Object type: <Unknown>
2024-10-25T12:53:26.178Z verbose: LOG EVENT: qseow-qix-perf:pro2-win1:INFO, QixPerformance.Engine.Engine, LAB\goran, 5b817efe-472d-43ce-8a31-6cce34af7de9, Doc::GetAppProperties, Object type: <Unknown>
2024-10-25T12:53:26.191Z verbose: LOG EVENT: qseow-qix-perf:pro2-win1:INFO, QixPerformance.Engine.Engine, LAB\goran, 5b817efe-472d-43ce-8a31-6cce34af7de9, GenericObject::GetLayout, Object type: appprops
2024-10-25T12:53:26.222Z verbose: LOG EVENT: qseow-qix-perf:pro2-win1:INFO, QixPerformance.Engine.Engine, LAB\goran, 5b817efe-472d-43ce-8a31-6cce34af7de9, Global::ConfigureReload, Object type: <Unknown>

[mountaindude]

To clarify a bit:

What I have seen on some QS environments is that log events from all other QS services are sent as UDP messages to Butler SOS, but no Qix engine events are sent.

So you could be seeing UDP traffic from QS to Butler SOS, just that it is not the Qix events, but rather other log events such as proxy events (users logging in/out, opening/closing apps etc)