73
Views
7
Comments
Service Actions log taking to much database space

Hi Guru's

So I love the personal cloud and service actions making everything working better. Only the log table oslog_SrvAPI_6 is growing unbelievable fast. Of course I can make a timer that cleans that Table every 5 min but just wanted to point this out and ask you guys if this is normal...

Greetz!


2020-10-28 09-51-07
Felipe Santos

Hello,


From what I understand, I think this application can help you "DB Cleaner on Steroids", if I'm not mistaken you can delete the records of some databases from time to time.

https://www.outsystems.com/forge/component-overview/5018/db-cleaner-on-steroids


sample.PNG
2025-07-14 13-53-13
Heryck Azevedo

Hello!  Another thing you can do is not save the integration logs, and for that you can disable the activity monitoring for a module from the Operation tab of the module in ServiceCenter. These rules apply for the module that the name appears on the URL (/ModuleName/rest/...).

That disables all screen, extension, integrations, ..., from the module while still giving you the errors.

Not sure how is your architecture or what else you have on your module that you need activity monitoring, but you have an isolated module just for your integration it is probably a good solution.

Kind Regards 


UserImage.jpg
freek

I think this is the way to go indeed all that logging is not needed.

The service Actions logging is set to default where can I find the default value?

2025-07-14 13-53-13
Heryck Azevedo

So that the module does not save the logs, this is the necessary configuration

UserImage.jpg
freek

Agree but what if I only want service actions trough the whole platform log only on troubleshoot. Can I change some where the default value?


UserImage.jpg
freek

Does anyone know where to set the default value for this?

2025-07-14 13-53-13
Heryck Azevedo

I'm not sure if I understood your problem well, but ... below is some information regarding the  logging levels.

The available logging levels for Service Action requests are the following:

Default
All requests are logged including some basic information (like the date and time of the request). No details regarding errors, request headers or payloads are logged.
Troubleshoot
On top of the information kept by the Default level, error details are also logged. Click on the "Error" link displayed on the right to get more details about the error.
Full
On top of the information kept by the Troubleshoot level, request headers and payloads are also logged. Click on the displayed "Error" link or, if there's no error, click on the "Details" link to obtain detailed logging information.
Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.