or other reporting applications, database administrators can create templates that analyze and format the audited output into valuable reports. Note that Groove Audit data is distinctly different from the Audit Log and Groove usage reports available from any Groove Server Manager installation. The following table shows how Groove Audit output differs from the data collected in Groove Server Manager reports: Groove Audit data Groove Server Manager Reports Groove Server Manager Reports – – Groove Usage and Activities Audit Log Groove client events Statistics relating to Groove users, Groove Server Manager events within a logged as they occur. workspaces, and tools over a date range. date range. For example: For example: For example: User1 created Domain member names and status Server startup workspaceA at (active, pending, deleted) Relay server added <date/time> Number of workspaces that a member Domain added User1 added has joined Discussion tool to New domain member added Names of workspaces created by a workspaceA member <date/time> Workspace names and creation dates User1 invited User2 to Workspace member names as of report workspaceA date <date/time> Number of users in workspace as of User2 entered report date Discussion tool in Names of tools in workspaces as of workpaceA report date <date/time> Number of minutes a tool was used during date range If auditing is necessary in a Groove collaboration environment, IT planners should follow best practices in place at their organization, along with these guidelines: Consider whether the Audit Log and Groove usage reports generated by Groove Server Manager will provide the type of data you need. If your organization requires Groove Auditing services, consider the available installation and setup options and select one most suited to your infrastructure and user population. Identify the Groove events that you want to audit.
or other reporting applications, database administrators can create templates that analyze and format the audited output into valuable reports. Note that Groove Audit data is distinctly different from the Audit Log and Groove usage reports available from any Groove Server Manager installation. The following table shows how Groove Audit output differs from the data collected in Groove Server Manager reports: Groove Audit data Groove Server Manager Reports – Groove Usage and Activities Groove Server Manager Reports – Audit Log Groove client events logged as they occur. For example: User1 created workspaceA at <date/time> User1 added Discussion tool to workspaceA <date/time> User1 invited User2 to workspaceA <date/time> User2 entered Discussion tool in workpaceA <date/time> Statistics relating to Groove users, workspaces, and tools over a date range. For example: Domain member names and status (active, pending, deleted) Number of workspaces that a member has joined Names of workspaces created by a member Workspace names and creation dates Workspace member names as of report date Number of users in workspace as of report date Names of tools in workspaces as of report date Number of minutes a tool was used during date range Groove Server Manager events within a date range. For example: Server startup Relay server added Domain added New domain member added If auditing is necessary in a Groove collaboration environment, IT planners should follow best practices in place at their organization, along with these guidelines: Consider whether the Audit Log and Groove usage reports generated by Groove Server Manager will provide the type of data you need. If your organization requires Groove Auditing services, consider the available installation and setup options and select one most suited to your infrastructure and user population. Identify the Groove events that you want to audit.
GrooveAuditPrescriptiveGuide.docx