One option is to use the session ID. In Qlik Sense, the session ID is unique for each session and can be retrieved using the function SessionId(). In NPrinting, you can use the session ID provided in the log files.
Another option is to use the client type. In Qlik Sense, the client type can be retrieved using the function ClientPlatform(). NPrinting sessions typically use a different client type than regular Qlik Sense sessions.
Finally, you can also differentiate between a user's session and an NPrinting session by analyzing the traffic on the Qlik Sense server. NPrinting typically generates a higher volume of traffic than regular Qlik Sense users, so you can use this to identify NPrinting sessions.
Using any of these methods, you can implement a filter in your report to differentiate between a user's session and an NPrinting session.
On your second question about "proxySessionPackage":
The "_proxySessionPackage" field in the Qlik Sense Session Monitoring app is related to the use of proxy services in a Qlik Sense deployment.
When a user accesses a Qlik Sense application through a proxy service, the proxy service creates a proxy session package that includes information about the user, the Qlik Sense server, and the requested application. This session package is then used to communicate with the Qlik Sense server on behalf of the user.
In the Session Monitoring app, the "_proxySessionPackage" field displays the ID of the proxy session package associated with a particular session. If this field is blank for some sessions, it may indicate that those sessions were not created through a proxy service.
