Audit log is a subsystem that records events on the Softswitch, with ability to filter by name/type/date.
It provides switch operator a tool to troubleshoot and investigate what changes were done, by whom and when to numerous components of the system, including Accounts, Customers, Tariffs etc.
Location on the Softswitch
The Audit Logs Viewer feature is available only for web users with Administrator privileges under Root Customer and can be accessed from System Management --> Tools --> Audit Logs Viewer
Sippy also has
- Resource - WHERE the event happened
- Action - WHAT exactly happened
- Action by - WHO accessed the page/did the changes
- Start Date/Time, End Date/Time - WHEN the event happened
A button with diskette image triggers Download for the filtered data.
A button with looking glass opens detailed report for specified entry, e.g.:
- Resource - WHERE the event happened. Contains the reference to affected subsystem, e.g. accounts or tariffs with corresponding ID of element that was touched.
- Action - WHAT exactly happened. Hover mouse button to the action to get pop-up hint. List of actions with description and syntax could be found in table below:
- Action by - WHO accessed the page/did the changes. Example of syntax:
1. [letter that corresponds to system unit]:
- u for Web Users
- a for Accounts
- c for Customers
- v for Vendors
- t for trusted XMLAPI call
2. [id of the entity]
e.g. for Web users it would be i_customer that owns this Web User. For Accounts, Customers, Vendors it would be i_account, i_customer, i_vendor correspondingly. For trusted xmlapi there would be 0.
3. [id of sub entry]
e.g. for Web users it would be i_web_user. For Accounts, Customers, Vendors, trusted xmlapi there would be 0.
4. [name of entry]
e.g. for Web users, Customers and Vendors it would have Web Login of Web User, Customer, Vendor correspondingly. For Accounts - Username, for trusted xmlapi there would be IP address of the Environment.
- Date - WHEN the event happened. Date is displayed in timezone of web user that checks the Audit log
- User IP/Node - where the request came from. Normally contains IP address of the user that participated in event, sometimes there could be a node-id of the system