Studio 2.2 Enterprise Edition includes a functionality called Auditing. To understand how Auditing works, please read the Auditing page on the OrientDB Manual.
By default all the auditing logs are saved as documents of class AuditingLog. If your account has enough priviledges, you can directly query the auditing log. Example on retrieving last 20 logs: select from AuditingLog order by @rid desc limit 20.
However, Studio provides a panel to filter the Auditing Log messages on a specific server without using SQL.
Studio Auditing panel helps you also on Auditing configuration of servers, avoiding to edit the auditing-config.json file under the database folder.
