Event Logs > Event Log- FAQ

You are here: Event Logs >Event Log- FAQ

The event auditing feature allows you to log details about user actions. For example you can configure this feature so that whenever a document is deleted, details about the action are logged. Details logged include the name of the user performing the action along with the date and time of the action.

The event auditing feature lets you keep a record of the actions of all Globodox users.

For example,

You can find out who deleted a document and when?

What time a user logged in on a particular day?

etc..

You can log information about almost any user action in Globodox. Events are divided into two categories, System Events and DB Events. You can choose to enable auditing of only System Events or only DB Events or both. Event auditing must be separately enabled for each Globodox DB.

To enable auditing of System Events...

1.	In Globodox, click the Globodox button.

2.	Click the Options button. The Options window will now be launched.

3.	Click the DB Options node. The DB options will now be displayed on the right pane.

4.	In the right pane, check the Enable Event Auditing option under Event Auditing.

To disable auditing of System Events...

1.	In Globodox, click the Globodox button.

2.	Click the Options button. The Options window will now be launched.

3.	Click the DB Options node. The DB options will now be displayed on the right pane.

4.	In the right pane, uncheck the Enable Event Auditing option of Event Auditing.

You should only select the events that are important to you. If you select all events for auditing then the event log will grow in size very quickly. For example if you decided to log the "Open Globodox DB" event and if you had 50 users using Globodox, then every time all the users opened a Globodox DB, 50 entries (one for each user) would be added to the log.

Yes, it does but only if you have chosen to log a lot of events or if you have chosen to log an event which occurs very frequently. When you enable event auditing and select an event to be logged, Globodox has to perform the extra step of logging information every time that event occurs. The time taken to perform this step will affect performance if a lot of events need to be logged.

To view the list of System Events which have been logged, click Settings > System Settings > Event Log. To view the list of DB Events which have been logged, click Settings > DB Settings > Event Log.

You can easily sort and filter events based on the Date of occurrence, Event type and Event Result.

To view events for a particular document select the document in the List View pane and click the Event Log tab on the Document Details pane.

Yes, you can delete entries from the log viewer. Please note that when you click the Delete button on the toolbar of the Event Viewer Window, only the selected entry will be deleted. Individual or selected log entries can be deleted by right-clicking the selected log entry and choosing the delete option.

When the log entries are deleted a new log entry recording the deletion of the log entries will be added to log. You cannot delete such log entries (In other words, you cannot delete log entries which record the deletion of other log entries).

Yes, you can export entries from the log viewer. Entries which meet the currently specified filter conditions will be exported in the CSV (Comma Separated Values) format. Files in the CSV format can be easily opened by applications such as MS Excel.

Depending on the amount of log entries you generate, we recommend that you export and then delete log entries from time to time. For example after six months of use, you can decide to, every month export and delete all log entries which are older than six months. You can set in a policy for storage and retention of the CSV files which contain the exported log entries.