Overview
System events are generated by TripBuilder and provide status and context information on different actions performed by the system. System Events can be found under the Cockpit Settings.
Since System Events are solely informative, they cannot be altered in any way by the user.
How to view System Events
Steps to view System Events:
- Go to Settings.
- Under the Monitoring menu, click on System Events.
The System Events page displays the option to perform a text search or to filter by severity.
The table of system events contains the following information:
- Created: date and time of creation
- Nezasa Trace ID (value presented as a toast notification when an error occurs)
- Severity: Info, Warn or Critical
- Type
- Action
- System
- Itinerary
- Title
- Actions: a + button that displays the details of the system event when clicked, and a COPY button that copies the system event's details to your clipboard, allowing you to paste them into other applications.
Sorting and filtering capabilities are supported by most of the columns, where, particularly for the Created column, a date range can be defined.
Examples of system events:
Type | Severity | Event Example |
apiCall |
Info |
Midoco Submission Response |
Warn |
Midoco Submission Request - Validation Warnings |
|
apiCallSuccess | Info | Midoco Submission Response |
CompanyStatusChange | Info | Tour Operator status change |
databaseOperation | Warn | Couldn't delete product refId=58cfda702f4nt4sy240a2 |
emailFailure | Critical | Email couldn’t be sent: Reservation request received |
emailSuccess | Info |
|
passwordReset | Info | Password Reset |
userSignUp | Info | User SignUp |
Alternatively, instead of clicking on the + button for each individual event to see its detail, the user can check the option Show descriptions of all system events, which will automatically expand the detail for each event entry.
Supplier events
The following events with supplier external systems are also stored as system events:
- Musement: Availability, Request, Book and Cancel
- SoftConEx: Availability, Request, Book and Cancel
- Aerticket HUB: Search, Verify, Book, Cancel and Retrieve
Data availability
System events are stored for a limited time period, after which they are deleted:
- 365 days: Booking, Booking Change and Cancellation events
- 30 days: all remaining events
Comments
0 comments
Article is closed for comments.