Audit Coverage by Session Type

Compare which events Workbench audits natively and which events OpenTelemetry covers, for each session type.

Workbench

Posit Workbench native auditing does not cover every session type equally. This page shows what Workbench records for each session type, and where OpenTelemetry is the alternative. For the settings, see Auditing Configuration.

Native auditing

Event RStudio Pro Positron Pro VS Code Jupyter
Authentication events (sign-in, sign-out, failed sign-in) Yes Yes Yes Yes
Session lifecycle (start, suspend, exit) Yes No No No
File upload and download Yes No No No
Console commands Input, or input and output R and Python input only No No

The Workbench server (rserver) writes authentication events, not the IDE session, so they do not depend on the session type. Session lifecycle, file transfer, and console events come from the session itself, and only RStudio Pro sessions write all of them. Enable event auditing with the audit-r-sessions setting. Enable console auditing with the audit-r-console setting.

OpenTelemetry

Event RStudio Pro Positron Pro VS Code Jupyter
Authentication events Sign-in only Sign-in only Sign-in only Sign-in only
Session lifecycle Yes Yes Yes Yes
File upload and download No No No No
Console commands No No No No

OpenTelemetry exports sign-in events (workbench.user.login), session lifecycle events (workbench.session), session state transitions, and session launch traces. It does not export sign-out events, console input or output, or file transfers.

Back to top