Enabling a concise user activity log
You can configure IZSME to generate a concise user activity log, with only the minimal information you need in order to diagnose problems quickly.
With concise user activity logging, you can tell what workspace a user visited; and which users have logged on. The resulting log presents the minimum necessary information so that the logs don't get too large. The user activity log can be controlled separately from other IZSME logging.
<ZOWE_INSTANCE>/workspace/app-server/serverConfig/server.json
For
security purposes, write access to this file should be limited to an administrator. For more
information on the server.json
file itself, see this example server.json file. "logLevels": {
"com.rs.tep.queryhandler.logonattempts": 3,
"com.rs.tep.queryhandler.useractivity:" 3,
}
The minimum logging level for the user activity log is 3.
The following are examples of log entries for logonattempts
and
useractivity
.
Logger: com.rs.tep.queryhandler:logonattempts
Log level used: 3
2021-05-05 23:29:55.969 <ZWED:22328> mshelby DEBUG (com.rs.tep.queryhandler:logonattempts,logonAttemptsLogger.js:25) Logon attempt {
user: 'sysadmin',
izSMEInstanceId: 'hUE5lYghwfBOtBKnaSrw',
tepsConfigurationId: '0904fd16-655a-4ec3-8ac2-e6c3ea8b70af',
status: 'SUCCESS'
}
The message status can be SUCCESS, FAILED, or ERROR.
Logger: com.rs.tep.queryhandler:useractivity
Log levels used: 3 (first example), 4 (second example)
2021-05-05 23:33:13.311 <ZWED:7460> mshelby DEBUG (com.rs.tep.queryhandler:useractivity,log-utils.js:99) User visits workspace {
workspaceId: 'deec9cbb19',
izSMEInstanceId: 'sV0v8O01lsln1Y4wn1MO',
navigatorPathString: 'Enterprise | z/OS Systems'
} 1620257593311.9
2021-05-05 23:33:13.312 <ZWED:7460> mshelby FINER (com.rs.tep.queryhandler:useractivity,log-utils-impl.js:15) User visits workspace with navigator path [
{ id: 'PHYSICAL_ENTERPRISE', type: 'ROOT', name: 'Enterprise' },
{ id: 'ed8cf67d@MVS', type: 'SYSTEMS', name: 'z/OS Systems' }
] 1620257593311.9
For more information on the log levels in Zowe, see Log levels.