TSL Logs

The TSL log records all system events associated with the polling, retrieval and verification of TSLs for the registered TSLs. The log records should be reviewed regularly to ensure TSL polling is being managed as expected.

Each item in the screenshot is described below:

Items	Description
Clear Search	After a Search this window will only show the filtered records. The Clear Search button is used to view the full set of records.
Search	This opens a new window where search criteria can be entered based on each column of the transaction grid.
Customise Columns	This opens a new window to configure which column need to be shown in the grid and which column need to be hidden. See below for more details
\|< < > >\|	These buttons are for navigating the different pages of the transaction log. Note: The number of records shown per page is configurable from within Global Settings.
Export Logs	This button is used to export the selected transactions log into a zipped CSV file in which each column is separated by literal '~&~'. The file can be viewed using Microsoft Excel. However, in order to view and analyze the contents of the file in detail (all the archived transactions etc.), the operator needs to import the file into ADSS using the Import Archived option.
Verify Integrity	Verifies the integrity of the TSL Monitor transaction log records. It detects tampered and deleted records and generates a report that can be exported to a physical drive.
Show Archived	This opens a new window where you can import and view previously archived file i.e. archived/exported transactions log.
Log ID	A unique serial number for the log record, it is system-defined and not part of the request/response messages.
Event ID	Identifies the TSL Monitor Event ID that generated the log record.
TSL Friendly Name	Identifies the TSL using its friendly name.
Performed At	Identifies when the system action was performed.
Message Type	Identifies the type of message (e.g. a system action, an information message or an error message).
Message	Shows messages generated by the system.
Show complete logs	By default it is unchecked and only shows the main conclusive message in TSL polling logs rather showing each and every step performed as part of TSL processing. The message either gives final statement whether the TSL is updated in database or ignored or failed. When checked system shows complete TSL logs.

The TSL Monitor Service transaction records can be sorted in either ascending or descending order by selecting a table column from the drop down list. From the drop down menu in above screen, choose Import Archived and click on Go button. This will show the following screen:

Items

Description

Import archived transaction file

Use this option to browse the archived log file in zip format from the operator machine. By using this option the archived log file is uploaded on the ADSS Server. It can be an expensive operation if the file is of large size so the operator is allowed to upload a file with maximum size up to 25 MB. Use the archived file path option for files bigger than 25 MB.

Archived transaction file path

Use this option if the file size is greater than 25 MB. This option does not upload the archived file to the server. Rather the server reads the file from given file path before importing which is faster than the above option. You can either specify the local file system path or a network path.

Note: Do specify the archived log file name in the file path.

The archived files were created in the csv format till ADSS Server v4.7.5 but from v4.7.6 and onward the archived files are zipped to save the disk space when archiving. If you are importing the archived files created using a pre-v4.7.6 deployment to ADSS Server v4.7.6 or later then first zip them before importing otherwise ADSS Server will not recognise them as correct archived files.

As explained above, clicking on the Search button on TSL Monitor Transactions Log Viewer displays following screen:

The Search button can be used to filter the records log. This is particularly useful when looking just for error messages, or messages generated within a particular date range. The filters can be combined to set-up advanced queries such as “show all errors generated whilst downloading TSLs” or “show all errors while verifyingTSLs”:

If "_" character is used in the search then it will act as wildcard.

Clicking on the Customise Columns button on TSL Logs displays the following screen:

By default all columns are in the "Selected Columns" list. In order to hide a column move the required column to "Available Columns" list.

Each log record within the database is protected with a cryptographic HMAC checksum to detect any intentional or accidental modification of records. Clicking the Verify Integrity button verifies the log integrity by checking each checksum and generates a report as shown below:

Click on the Export Logs button to export the request/response to a network file. Clicking the Fix HMAC Errors button will re-calculate the HMAC for tampered transaction logs records for this module.

Note: This option will not detect the unauthorized deleted records but it will only fix the unauthorized modifications and/or ambiguous records for which HMAC value is not present/incorrect.

The Verify Integrity feature is available for the transactions log of all services within ADSS Server.