Team Audit Logs

All Parsec user connections and all administrative actions are recorded as auditable log events.

Downloading audit logs through the Parsec admin dashboard

A subset of the audit logs can be downloaded in JSON format from the Parsec admin dashboard, limited to 7 days history and a maximum of 5000 events. 

Downloading audit logs through the API

Parsec for Teams Enterprise customers can download audit logs through the API, without limitations on history. For further details see the API documentation.

Log Format

Logs are recorded as events in the following format:

Email

The email of the user that took the action that recorded the event. This is the accounts current email, not the email when the event was recorded.

Event Name

The name of the action taken.

Timestamp

When the event was recorded.

Team ID

This will always be the ID of your team.

Data

JSON properties specific for each event.

Connection events

Several events are recorded when a client connects to a host. Wherever applicable connection events are recorded both from the client's perspective and from the host's perspective. Most events contain an exit_code in the data column indicating the status of the connection. See the support article about exit codes for details.

conn_client_offer

The client has made a request to connect to a host.

conn_signal_offer_relayed

The backend has approved and relayed the client's offer to connect to the host.

p2p_client_complete

A connection attempt has been completed (successful or unsuccessful). See exit_code in the data column for status.

p2p_host_complete

A connection attempt has been completed (successful or unsuccessful). See exit_code in the data column for status.

client_disconnect

The connection is over for the client. See exit_code in the data column for status.

client_disconnect

The connection is over for the host. See exit_code in the data column for status.

Common data properties for connection events:

Attempt ID

The Attempt ID is a unique ID persistent for the duration of each Parsec peer-to-peer connection.

Host User ID

The User ID of the host in connection events. For shared Team Computer's this will be 0.

Host Peer ID

Host Peer IDs are persistent as long as a user is logged in on a device but may change if the user logs out and then logs in again on the same device.

Client User ID

The User ID of the client in connection events.

Client Peer ID

Client Peer IDs should not be relied upon to stay persistent between peer-to-peer connections.