vWorkspace

Last reply by 04-24-2015 Solved
Start a Discussion
3 Argentum
175027

Secure Access "Gateway" logging level

We run our Secure Access with logging turned on for security reasons. Version 8.5's logging is creating extremely larger log files as compared to 8.0.1 and filling the disk in a short period of time.

Is there a setting or registry or file to edit to change the amount of logging. For security reasons we only need client connection information.

Thanks,

-Greg Polen
Texas A&M University

Home: Venue 11 vPro 7130 A01, Inspiron 3521, XPS 8700, PowerEdge T110
Work: OptiPlex 9010, PowerEdge 2950, R710, R720, R730

Solution (1)

Accepted Solutions
2 Bronze
2 Bronze
537

Unfortunately there aren't different logging levels for Secure Access.

You could try using procmon logging instead. You could create a procmon filter that only displays client connection information, and set the option that tells procmon to drop filtered events.

The only downside is when procmon runs for a few days it can hog up all available memory, so you may need to restart procmon once per day.

The only other downside is that logging (either procmon or file based) reduces performance but that doesn’t seem to be an issue for you since you have file based logging on anyway.

View solution in original post

Replies (2)
2 Bronze
2 Bronze
538

Unfortunately there aren't different logging levels for Secure Access.

You could try using procmon logging instead. You could create a procmon filter that only displays client connection information, and set the option that tells procmon to drop filtered events.

The only downside is when procmon runs for a few days it can hog up all available memory, so you may need to restart procmon once per day.

The only other downside is that logging (either procmon or file based) reduces performance but that doesn’t seem to be an issue for you since you have file based logging on anyway.

3 Silver
537

Hi Greg,

Could you enable the vWorkspace reporting database and utilise the Diagnostics and monitoring reporting to gather the client connection information?

Or if the users are just coming in from Web Access would IIS logging be enough? You might have to use IIS for the secure HTTPS connection rather than use the Web proxy of the SAS server in order to get the "originating client IP"..

Thanks,

Sam

Latest Solutions
Top Contributor