Event logs

The event logs are a way to audit important events that occurred on the SECollab server. Each event has generic properties (shared with all types of events) and specific properties.

Shared properties

• Date: the date of the event
• Author: the author of the event (may be a user or an agent)
• Project: the project related to the event (can be empty for server events or deleted project events)
• Category: the type of event
• Affected Object(s): resource related to the event (project, design, user, etc.)

Advanced properties

Some events may need to log more complete technical information. To this end, each events can contain specific properties (key/value), displayed in the "Advanced Properties" column. This column supports textual filtering.

Project related events

Event logs are created for the 3 categories below:

• Project created
• Project archived
• Project deleted

Regarding deleted projects, since they're not accessible anymore, the "Project" column is empty. The name of the deleted project is visible in the "Affected Object(s)" column. If the user clicks the link, a standard unreachable resource error message is displayed.

User related events

Event logs are created for the following user management actions:

• Server-scoped actions
  • User created
  • User archived
  • User deleted
  • Login (through the web browser login screen)
  • Login failed (through the web browser login screen)
• Project-scoped actions
  • User added to project
  • User removed from project

With these events, it becomes possible to find active users by filtering login events on a given date range, or to keep track of excessive failed login attempts with an invalid user or password.

Design related events

Event logs are created for the following design actions:

• Design published: success or failure of a design publication (details in the event's advanced properties)
• Design modified: the title of a design has been updated
• Design deleted

With the "Design published" event, we can see agent publications, automated or manual, and whether they succeeded (with or without warnings) or failed. This enables detecting projects with or without any publish activities, as well as monitoring publication incidents (e.g.: abnormally high count of failed publications). A textual search on advanced properties can be useful when interested only in successful/failed publications, or in a given tool.
Automated publications by agents using polling (TestLink or Hopex for instance) will not be logged in case the authoring tool is not accessible.

Filtering and exporting the event logs

Each column of the event logs can be filtered (and can be combined with other filters):

• Date: date range
• Author: multiple selection among server users
• Project: multiple selection among existing projects
• Category: multiple selection among available event types
• Affected Object(s): textual search, non case sensitive
• Advanced Properties: textual search, non case sensitive

Clicking the Reset all filters button reverts the table to its initial state, without any active filters.
Clicking the Export button will open a confirmation modal to export the event logs. The export accounts for active filters in the table. After confirmation by clicking the OK button, the export file is timestamped and downloaded to the download folder of the web browser.
The downloaded Excel file contains the same rows and columns as those displayed in the event logs table at the time of the export, except that results are not paginated, and that a maximum of 100000 events can be exported.