Hello,
In my company we are currently recovering the file import logs in SAS Studio. Thanks to this file :
Here is an example of an log import file:
However, we notice that the SASStudioMidTier3.81.log file generates a large amount of logs and that since we generate all these logs we notice a huge slowness to access the SAS Studio services:
Indeed we access the session after 20 minutes, sometimes we have to restart the session.
Moreover when we access the session it is very slow and therefore not usable.
Is there a way to correct this? A way to choose which logs are generated in the file? Or another file where to find the import logs?
For example we have the logs of file download in the files localhost_access_log*, being with the paths C:\SAS\ModelMgr\Lev1\Web\WebAppServer\SASServer1_1\logs\localhost_access_log*
Is it possible to generate file import logs in these localhost_access_log* files?
Thanks by advance for your help.
but how do I know if the file import logs are in :
What is it that you are trying to do?
It sounds like you are perhaps trying to track whether users have been using the SAS/Studio interface to upload files? Is that correct?
Is there some reason why you need to track that? For example if the users are using SAS/Studio processes running under their own accounts ANY file they saved on to the server were SAS runs should be owned to their account already. Why does it matter whether it was uploaded or created by running a SAS program?
I want to know when a user imports a file.
I already get the logs of the downloaded files in the file C:\SAS\ModelMgr\Lev1\WebAppServer\SASServer1\logs\localhost_access_log*
The only thing missing is the logs concerning the imported files.
This tracking is imposed by my company to respect the GxP rules.
When you say "The log line should include the category that is writing the message, but your screen shot does not" what do you mean ?
The entire log is like this :
If DEBUG is the level of the log, what call you the category ?
It's work !
Thank you very much for all yours explanations 🙂
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.
Find more tutorials on the SAS Users YouTube channel.