RStudio Connect records information about changes to the system. These events
can be obtained for auditing purposes. Audited information is available in the
RStudio Connect dashboard, by using the auditing
endpoints in the Connect Server
API, using the
administrative command, or through an optional log file.
The auditing system cannot be disabled and always records changes to the RStudio Connect database.
This table contains the event types logged by the auditing system:
||Create a user|
||Change an existing user|
||*Delete a user|
||Set or remove a lock for an existing user|
||Add new content|
||Upload a bundle for a content|
||Deploy content to the server. Content may need to be published after deployment.|
||Change content settings|
||Activate a token. Tokens are used by the
||Create a group|
||*Change an existing group|
||Delete a group|
||Add a user to a group|
||Remove a user from a group|
||Give a user view or edit access to content|
||Remove a user from view or edit access list|
||Give a group view or edit access to content|
||Remove a group from view or edit access list|
||Change from a specific list of viewers to "just me"|
||Add API key|
||*Change an existing API key|
||Remove API key|
||Add vanity URL|
||Update vanity URL|
||Remove vanity URL|
||Remove a bundle|
||Download a bundle|
||Create a tag/category|
||Delete a tag/category|
||Update a tag/category|
||Associate a tag with some parent tag/category|
||Associate a tag with content|
||Disassociate a tag with content|
||Change to application environment variables|
||A user has started a dashboard session|
||A user needed to re-authenticate for a privileged action after a WebSudo timeout|
The events marked with an asterisk can only be performed using via the
usermanager administration command.
Audit Log File#
This section describes a deprecated logging implementation which will be removed entirely with RStudio Connect's November 2022 edition. See the logging documentation for additional details.
Audited events can be optionally written to a file.
configuration setting controls whether or not auditing records are written to
disk. By default,
Server.AuditLogFormat has the value
indicates that auditing information is not written to disk.
JSON will write to the file
named by the
Server.AuditLog writes to
Server.AuditLog file is created only when the
permits on-disk logging.
Audit log files contain actions performed through a specific RStudio Connect server. In a clustered installation, the auditing files from each server need to be combined.
The Connect dashboard, Server API, and
usermanager tool present all
auditing information, not per-server records.
This configuration example enables CSV audit logging and is using the default audit log location.
; /etc/rstudio-connect/rstudio-connect.gcfg [Server] AuditLogFormat = "CSV"
This configuration example enables JSON audit logging and writes to a different file name.
; /etc/rstudio-connect/rstudio-connect.gcfg [Server] AuditLogFormat = "JSON" AuditLog = "/var/log/rstudio-connect.audit.json"
RStudio Connect will refuse to start if the
Server.AuditLog file already
exists and has content that appears to contradict the format requested by
Server.AuditLogFormat. In other words, if the file looks like it is in
CSV format but the configuration requests JSON or looks like JSON and the
configuration requests CSV, the server will not start.
The CSV audit log format has fields written in the following order:
The database ID of the audit log record.
The timestamp of the record, in RFC 3339.
The database ID of the user that performed the action.
The description of the user.
The action the user performed.
The description of the event.
When formatting entries in JSON, each text line written to the audit log file
will be a single, complete JSON object with the same data as for CSV with
The specification of the JSON object is the one used for Audit Logs in the Connect Server API.
usermanager administration command-line
tool can produce CSV and JSON containing auditing records, and can also filter
by time interval. See the Command-Line interface appendix
for more information about the