Accessing Logs as an Instructor¶

Abstract

This article is a guide for instructors on accessing logs for their courses, along with details of the information that can be viewed in the logs.

How to View Logs¶

Begin by navigating to your course. Within the controls to the right of the course description, click the View Logs button.

The "View Logs" button is located in the course controls, after the "Connected Apps" button.

This will take you to the Logs page, where you will see a table of information recorded about actions taken within the course.

Logs Table¶

The table on the Logs page contains the following columns:

Timestamp: the date and time (in UTC) of the action taken
Organization: the organization that the course is in
User: the user that performed the action
Action: a brief description of the action taken
Result: indicates whether the action completed successfully
Details: provides more technical details on the action and the exercise affected

Note

Please note that in the "User" column, you may see names like orchestration-service, job-api, or sync-service. These are automated processes that act in courses that the Virginia Cyber Range records in logs to make sure all actions that occur are viewable.

Above the Logs table are various filter fields that can be used to sort through log information.

Date: allows for searching a specific date or a range of dates
Organization: allows for searching for logs from specific organizations
Status: allows for searching between successful and failed actions
User ID: allows searching for actions performed by a specific user, using the User ID from their profile page
Object ID: this field will automatically populate your course ID

The filter fields are after the "Logs" header.

What Information is Recorded in Logs?¶

While the Virginia Cyber Range does not keep track of activity that happens within a VM, logs track changes to Cyber Range entities like courses and users.

Some examples of changes to your course that are logged include creation of the course, adding and deleting exercise groups within the course, requesting support in the course, and creation of a course code.

Examples of user interactions within the course that are logged include users joining or being removed from the course, users interacting with exercise environments in the course (starting, joining, stopping, and reinstalling), and updating teams.

Have a Question? Contact Support¶

We're here to help you. If you still have questions after reviewing the information above, please feel free to submit a ticket with our Support Team and we'll get back to you as soon as possible.