About Real-Time System Logs

Log messages follow a standard structure that provides information about the source, time, and type of event that generated the message.

The following table describes the elements in the message structure.

Element	Description
User Name	If the message was generated by an action or event related to a test session or user action, the user name is displayed. N/A is displayed for user-independent system messages. User Logins can be from Landslide Client (or Standalone Client), Tcl API, REST API, or TeX.
Time stamp	The date and time the message was generated, converted to the client platform's local time zone. If the test system and the client are in different time zones, time stamps displayed in the Real-Time Log will differ from corresponding entries in the Test Log.
Severity	The importance of the information included in the message. The messages are also color-coded to allow you to easily identify warning and error messages. Informational messages record normal activity such as database changes and test commands, and are identified by White text. Warning messages record discrepancies in the system such as TAS and test server software incompatibility, and are identified by Yellow text. Error messages record operator errors such as an incorrect test definition, and are identified by Orange text (these errors are usually also displayed to the user in a pop-up window). Fatal Error messages record system events that are serious enough to interfere with test system operations, and are identified by Red text.
Log type	The log type is used to filter the messages that can be viewed based on the user's permissions.
Verb	The action that generated the message: Create, Delete, Download, Export, Import, Login, Modify, Run (test session), Shutdown, or Upload. Additional details below for Login/Logout and REST API Requests.
Message source	The ID of the test session or the name of the process associated with the message.
Message detail	The text of the message.

User Logins can be from Landslide Client (or Standalone Client), Tcl API, REST API, or TeX.

sms 2023-04-09 12:08:30 Informational Operations Login User sms logged in from [email protected]:60017 as Super User
Client=GUI user=dan timezone=America/New_York os=Windows 11
sms 2023-04-09 12:08:39 Informational Operations Login User sms logged in from [email protected]:60018 as Super User
Client=REST agent=PostmanRuntime/7.31.3
sms 2023-04-09 12:08:46 Informational Operations Login User sms logged in from [email protected]:60021 as Super User
Client=Tcl user=dan timezone=America/New_York os=Windows 11
sms 2023-04-09 12:08:54 Informational Operations Login User sms logged in from [email protected]:60028 as Super User
Client=TeX agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv
sms 2023-04-09 12:12:37 Informational Operations Login User sms logged in 35 times from [email protected]:51000 as Super User
Client=REST agent=curl/7.58.0
sms 2023-04-09 18:35:30 Informational Operations Login User sms logged in from [email protected]:53171 as Super User
Secure=TLS Client=GUI user=dan timezone=America/New_York os=Windows 11

Because HTTP Basic Auth is used, REST API can be operated without a true Login and Logout, thus these actions are approximated by keeping track of a login key (username + client IP address + user-agent) and first request for a new login key is handled like a Login. For the REST API, they can optionally be persistent connections. See the REST API Requests section at the end. If using Secure/TLS connection , see Secure=TLS to start the user-agent section.

The key things to search for logins, it VERB=Login and Message " logged in ". The form is "User <username> logged in "

User Logouts

Standard Logouts initiated by the user:

sms 2023-04-09 12:19:02 Informational Operations Login User sms logged out from [email protected]:60012
Client=GUI user=dan timezone=America/New_York os=Windows 11
sms 2023-04-09 12:19:07 Informational Operations Login User sms logged out from [email protected]:60021
Client=Tcl user=dan timezone=America/New_York os=Windows 11

If REST API user calls POST /logout:

sms 2023-04-09 11:43:40 Informational Operations Login user sms logged out from [email protected]:53031
Client=TeX agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv

Idle Logouts:

Activity Monitor can forcibly logout clients if idle for too long. The idle time is adjustable via TAS Settings max_client_inactivity_hours and max_rest_idle_mins.

For full Clients, the form is like this:

<system> 2023-04-09 11:27:57 Informational System Activity Client for user sms logged out due to inactivity from [email protected]:52793
Client=GUI user=dan timezone=America/New_York os=Windows 11
sms 2023-04-09 11:27:57 Informational Operations Login User sms logged out from [email protected]:52793

Where the Activity covers the Activity Monitor action of closing the connection, logged as user=System and action/verb=Activity and the actual Client logout is logged as user=<User> and action/verb=Login.

For Persistent Connection REST API (or TeX) the form looks like this:

<system> 2023-04-09 12:14:55 Informational System Activity Connection for user sms logged out due to inactivity from [email protected]:60018
Client=REST agent=PostmanRuntime/7.31.3

Since there is no full login for REST API, there is just the one log by the Activity Monitor, user=System and action/verb=Activity.

Error Logouts:

If an attempt to login without HTTP Basic Auth:

<system> 2023-04-09 12:08:52 Warning System Login HTTPClient:[email protected]: REST API Message received with no Authorization header, closing connection

REST API Requests

Since HTTP Basic Auth is used for REST API, each request can be the first login or could be some intermediate request, and thus not every request is logged. Instead a login key is maintained based on the username, client IP-Address, and User-Agent. e.g. sms+10.71.14+curl/7.58.0. This is then used to track total request by that login key and reported every few minutes, like this:

sms 2023-04-09 10:47:36 Informational Operations Login User sms logged in 35 times from [email protected]:53220 as Super User
Client=REST agent=curl/7.58.0

The port indicated might only be for one connection out of many that this login key is used, since it doesn't have to use persistent connection. Do not trust the Port as fixed unless using persistent connection.

If no requests are made by this login key, the login key is kept in memory for up to 2 minutes. If no REST request is received in 2 minutes, that login key is released and a message is logged :

<system> 2023-04-09 10:42:40 Informational Operations Login Released 1 RESTful API Clients

This is not closing any sockets, but just releasing the login key that was used to throttle the login messages.