Simple question. Is there a way to disable the app-access log files in a tomcat environment?
The app access logs are controlled by the application that hosts the CA Clarity application. So if you are using tomcat then app-access.log is controlled by the tomcat logging configuration. This means that any logging changes that can be made against tomcat can be made against the tomcat that is hosting clarity. There are many articles on the internet describing how to modify the app-access logging, what gets logged, how it is displayed and how large it lets the file get before rolling it over.
Thanks and Best Regards,
Sr. Support Engineer
CA Clarity Support
not really a simple way. You can go into the %tomcat%\conf directory and modify some of the server.xml files. The trouble is when you do an add or remove it will overwrite your changes. You can edit the template files in the clarity directory as well so that the overwritten changes will get replaced with the add/remove. But I would recommend you just setup a cron job or a scheduled task to delete files that are older than a certian age instead. That way in the "freak occurance" that Clarity has an error. That you can see what the users were doing around the time of the error.
windows - Batch file to delete files older than N days - Stack Overflow
Are you saying that the work around is to specify altenate location for the log files so the people can't find them:
Can that be done for the access log only?
you can change the logging format so that they don't produce anything. Or you can change the directory to where they are logged. but if you restart the services, I think this value gets changed/overwritten.
Retrieving data ...