Viewing the Session Event Log
The Session Event Log records all activity during a Megaport Portal session, including the date and time of each event. Event logs can be useful when troubleshooting an issue.
The Session Event Log will become available in the Portal when the user performs an action that triggers it.
Note
- The Session Event Log is cleared when you refresh the browser or log out of the Portal.
- The Session Event Log records similar information to the Activity Logs. Activity logging captures all API calls, including those made outside the Portal (for example, through customer integrations), whereas session event logging is limited to actions performed within the Portal. For more information, see Viewing Activity Logs.
What information is logged
The system logs these session events:
- Configuring, deploying, and updating services (successful or failed)
- Approving, denying, or canceling a speed change
- Approving or denying connections
- Updating Port terms
- Terminating services
- Registering payment cards and making payments
- Setting up service keys
- Enabling Multi-Factor Authentication (MFA)
- Signing up for or logging in with Single Sign-On
- Updating user profiles
- Creating a company profile or Megaport Marketplace profile
- Setting up billing markets
- Saving and managing configurations
- Updating user notification settings
- Managing users
- Encountering issues during the ordering process
To view the event log
- Log in to the Megaport Portal.
- After you perform an action that triggers a log event, click the Event Log icon.
The icon changes to alert you to a new successful event, warning, or error.
The Session Event Log page appears, showing successful events, warnings, and errors for the current Portal browser session.
What information isn’t logged
The Session Event Log does not provide usage or billing information for a Megaport service, such as performance for a VXC or IX, or how much it costs. For more information about VXC billing, see VXC Pricing and Contract Terms. For more information about MCR usage, see Monitoring MCR.