Visual Guard does not include this feature yet.
However, you can directly access the log table (VG_LOG) from your application.
We left the data in this table clearly visible on purpose,
so that VG users can access or remove some records whenever they need.For instance, you can stop logging or partially clean-up this table when a given quota is reached.
This would be done by your own code in your application.

Visual Guard .NET

2nd question: Ok so how much will the auditing information grow over time for:

* Standard audit logging configuration?
* Verbose audit logging configuration?

Actually, it's difficult to evaluate
1 - You can turn on/off the auditing feature in VG Console
(this feature keeps track of who did what in the Console).
But this is not where most of the volume comes from.
As mentioned above, if you declare 5000 Users, you can expect the repository to increase by ~5 MB

2 - When it comes to audit your application,
you will add a few instructions in each event you want to log in VG repository.
It's not just a binary on/off situation anymore.
The number of logged events may widely vary from 1 application to another.
Then you have to multiply the number of events by the number of user and the number of transactions they make...
Bottom line, only the experience will give you an accurate evaluation of the size of your log for each application.
At this point, you will probably want to adjust the number of events you log, or the capacity of your dabatase...


Visual Guard .NET

Visual Guard .net stores the log in tables (in the repository). It is possible to reuse and re analyse this log in other tools that Visual Guard.Net.



Visual Guard .NET

In the console, you can access the log for each application (including the console) either through the menu Action/Event Log or with the right click/ Event Log.
You can declare events of your choice that you would like to track, and then, export it as a PDF document.



Visual Guard .NET

As you know, VG provides logging and auditing features.
By default, VG will log events in its repository.
You can also add more trace listener if you want (DBMS, file, OS, ...).
Then, you will be able to use VG Auditing features (log viewer, filters, pdf exports, etc...)


answer 15/07/08

When calling VG API an app can list all the users who access to it, including their roles.
From VG console, you can generate a complete report about the secured apps, the users, their roles and permissions.


Visual Guard .NET

You can log any event in your application (when the user enter/leaves the application, enters a form, views/edits/deletes a record...
You will add standard Visual Guard .Net instructions in your code each time you want to log a new event.
You can also send parameters to enrich the log (amount of a transaction, ID of the record modified, previous/new value of a field, ...)



Visual Guard .NET 

You can log any event in your application (when the user enter/leaves the application, enters a form, views/edits/deletes a record...
You will add standard Visual Guard .Net instructions in your code each time you want to log a new event.
You can also send parameters to enrich the log (amount of a transaction, ID of the record modified, previous/new value of a field, ...)



Visual Guard .NET

In the console, you can access the log for each application (including the console) either through the menu Action/Event Log or with the right click/ Event Log.
You can declare events of your choice that you would like to track, and then, export it as a PDF document.



Visual Guard .NET

Yes it does.

Visual Guard

The documentation generated with the console is not locked. You can modify it thanks to PDF Acrobat.
You may also access the log directly from your application and generate the rapport with your own tools. The logged information is stored in a table of the Database.


Visual Guard .NET