Logged Events
This section lists the events that are logged for each of the SuperSTAR components, as well as what data is logged in each event record.
Common Data
All event records contain the following information:
Key | Description | Example |
|---|---|---|
| The time the event occurred (UNIX timestamp, in UTC). The accuracy of the timestamp information depends on the machine where the event logger is running. | 1361592000 |
| A thread ID. | 42 |
| The action being logged. See the tables below for more details about the actions that are logged by each application. | login |
| The username of the user who generated the event. For Job Queue Manager (JQM) log entries from version 9.18 onwards, the The separate | johndoe |
| The groups this user belongs to. | [ group1, group2 ] |
| The name of the source application that generated the event. | SuperWEB2 |
| The name of the host machine that generated the event. | myhostname |
Some event records include additional data, which is listed in the tables below.
SuperWEB2 / Job Queue Manager / Open Data API
Action | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| The type of event:
|
Field | Description | SW2 | JQM | ODAPI | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| The source IP address of all user-initiated logged events. | ✔ | - | ✔ | ||||||||||||||
| A unique ID for this tabulation request. The same ID is recorded in the SuperSERVER log for events relating to this tabulation. | ✔ | ✔ | ✔ | ||||||||||||||
| If the TXD is very large it will be split into multiple parts (up to 60,000 characters per part). When a TXD has been split in the logs, this will indicate which part this record relates to for a given | ✔ | ✔ | ✔ | ||||||||||||||
| This will be present when the
| ✔ | ✔ | - | ||||||||||||||
| This will be present when the
| ✔ | ✔ | - | ||||||||||||||
| This will be present when the For saved tables it will be a UUID, while for JQM jobs it will be a simple integer. | ✔ | ✔ | - | ||||||||||||||
| This will be present when the | - | ✔ | - | ||||||||||||||
| The username of the user who submitted a query to Job Queue Manager. | - | ✔ | - | ||||||||||||||
| The output format of the Job Queue Manager query.
| - | ✔ | - | ||||||||||||||
| The format of a downloaded item.
Downloads of JSON, TXD and SDMX Structure.xml file formats are not recorded as these are structural formats and do not contain data. | ✔ | - | - | ||||||||||||||
| When
| ✔ | - | - | ||||||||||||||
| The duration of the event in seconds. In the case of a | ✔ | ✔ | ✔ | ||||||||||||||
| The TXD used in the query (up to 60,000 characters). | ✔ | ✔ | ✔ | ||||||||||||||
| A unique ID for this TXD. This can be used to link events relating to a single table. | ✔ | ✔ | ✔ | ||||||||||||||
| The unit record data columns that were displayed. | ✔ | - | - |
SuperADMIN
Action | Description | Additional Data | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| An administrator has logged into SuperADMIN. | |||||||||
| An administrator has logged out of SuperADMIN. | |||||||||
| A group has been created. |
| ||||||||
| A group has been removed |
| ||||||||
| The display name for a group has been changed. |
| ||||||||
| A user has been created. |
| ||||||||
| A user has been removed. |
| ||||||||
| A user has been added to a group. |
| ||||||||
| A user has been removed from a group. |
| ||||||||
| A user's display name has been changed. |
| ||||||||
| A user account has been locked. |
| ||||||||
| A user account has been unlocked. |
| ||||||||
| A user has changed their password. |
| ||||||||
| A user has reset their Open Data API key within SuperWEB2. |
| ||||||||
| A dataset has been added to the catalogue. |
| ||||||||
| A dataset has been removed from the catalogue. |
| ||||||||
| The location of a dataset's SXV4 file has been changed. |
| ||||||||
| The display name of a dataset has been changed. |
| ||||||||
| A user has been granted access to a dataset. |
| ||||||||
| A user's access to a dataset has been revoked. |
| ||||||||
| A group has been granted access to a dataset. |
| ||||||||
| A group's access to a dataset has been revoked. |
| ||||||||
| A data control method has been added or removed from this dataset. |
| ||||||||
| A statistical function has been added or removed from this dataset. |
| ||||||||
| A setting has been changed for this dataset (such as changing the |
| ||||||||
| The user has been granted access to a field. |
| ||||||||
| A user's access to a field has been revoked. |
| ||||||||
| A group has been granted access to a field. |
| ||||||||
| A group's access to a field has been revoked. |
| ||||||||
| The user has been granted access to a folder. |
| ||||||||
| A user's access to a folder has been revoked. |
| ||||||||
| A group has been granted access to a folder. |
| ||||||||
| A group's access to a folder has been revoked. |
| ||||||||
| The user has been granted access to a value. |
| ||||||||
| A user's access to a value has been revoked. |
| ||||||||
| A group has been granted access to a value. |
| ||||||||
| A group's access to a value has been revoked. |
| ||||||||
| The user has been granted access to a value set. |
| ||||||||
| A user's access to a value set has been revoked. |
| ||||||||
| A group has been granted access to a value set. |
| ||||||||
| A group's access to a value set has been revoked. |
| ||||||||
| The client that generated the event. This can be one of the following:
|
SuperSERVER
Action | Description | Additional Data | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Details of the query. By default this will include details of the fact tables and fields, but you can use the |
| ||||||||||||||||
| A cross tabulation job has been submitted to the server. |
| ||||||||||||||||
| SuperSERVER has started processing a cross tabulation job. |
| ||||||||||||||||
| A cross tabulation job has completed successfully. The event record includes the job ID and the time taken to complete the tabulation (in seconds). |
| ||||||||||||||||
| The cross tabulation results have been retrieved by the client. |
| ||||||||||||||||
| A unique ID for this tabulation request. The same ID is recorded in the SuperWEB2 log for events relating to this tabulation. |