Article Number: 000055118 | Last Modified: 2018/11/01
Description
We need to analyze the NPrinting log file to track user login and session duration. However, we couldn't find any official document about NPrinting Log File structure. 1. For us to capture usage stats (login and logout), how should we process the NPrinting log? Which could be identified as "Successful User Login", "Unsuccessful Login" and "User Logout/Disconnection"?
Resolution
we couldn't find any official document about NPrinting Log File structure. Log file structure available here: https://help.qlik.com/en-US/nprinting/November2017/Content/AdministeringQVNprinting/Logging/Logging.htm
1. For us to capture usage stats (login and logout), how should we process the NPrinting log? Not possible as log out is not recorded in the logs Logging IN is recorded in the WebEngine_Dev logs. DEBUG mode must be enabled: https://help.qlik.com/en-US/nprinting/November2017/Content/AdministeringQVNprinting/Logging/Logging.htm
2. Could we know the message types? Which could be identified as "Successful User Login", "Unsuccessful Login" and "User Logout/Disconnection"? As mentioned above, there is no log entry for Logout. These are the possible log entries under different Login types
NPrinting login successful: Webengine logs: no record Webengine_dev logs: "Login called for user "
Windows login successful: Webengine logs & Webengine_dev logs: "Windows login successful. The user with id has been correctly identified as a Windows domain user with sid indows login unsuccessful - both logs: If the domain user does not exist: No record If the domain user exists but the password is wrong: No record If the domain user exists, password is correct but Domain account user is not mapped to an NPrinting user: "Windows login failed. The user could not be associated to their Windows security identifier (sid)."
Get Answers
Find Answers
Qlik Community
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Experiencing a serious issue, please contact us by phone. For Data Integration related issues please refer to your onboarding documentation for current phone number.