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.
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"..
DELL-Joel W1
15 Posts
0
April 13th, 2015 10:00
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.
DELL-Sam H
57 Posts
1
April 24th, 2015 15:00
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