I'm not sure what dictates the frequency behind the file creation, but if you wanted to disable your PegaRULES-SERVICES-PAL, you can. I know of some customers who have done so. There is no real risk involved in that as far as I know. If you feel more comfortable you could change your <priority value="info"/> in your category name="ServicePAL" to a higher level such as "error" or "fatal".
But the level that we generate for services I believe are all at the info level anyways. So it will likely be equivalent to just disabling it. You are welcome to test different levels and see if the file size does not grow as much. But I believe it will essentially be an all or nothing affair.
If you run into any issues with your services that you would like to debug, you can always turn it back on. But in most cases when we want to analyze a service issue the relevant data is contained in the PegaALERT logs such as the alerts below.
PEGA0011 - Total request time exceeds limit Service Total Time
PEGA0012 - Outbound mapping time exceeds limit Service Mapping Time
PEGA0013 - Activity interaction time exceeds limit Service Activity Time
PEGA0014 - Inbound mapping time exceeds limit Service Interaction Time
PEGA0015 - Data parsing time exceeds limit Service Parse Time
Thanks for your reply Rett. Can you also tell me which triggers this file generation? The reason I am asking is these files do not get generated daily, so there should be some reason which triggers the generation. Should that be a long running web service or interaction? But in that case we generally face latency related to long running services daily but we do not find the files everyday, that is why I am confused.