If we running the tool to update the value is it stop the our running applications services?
Hi Ricardo,
It seems to me that logs in outsystems have a maximum length of 2000 characters. Am I correct? If so, is there any way to change this maximum length?
Thank you.
Hello Ana,
What logs are you referring to? Different kind of logs have different restrictions in different fields.
Are you talking specifically about the size you can add to the message in Audit action (which ends up in General Log) ? Yes, that is restricted to 2000 characters and cannot be changed.
If you need to log larger amounts of data, I recommend you create your own database table for it and use the Asynchronous Logging extension to insert data into it.
Best regards,
Ricardo Silva
Can you provide me some example on how to use this extension, so I can quickly test its functionality?
I'm getting the error "Unable to convert to record". I think I'm not doing this right and I didn't find any examples on the web..
Actually, let me provide some more information on this:
We need to log information for requests and responses either through outsystems modules or through .NET extensions.
Currently, we're using GenericExtendedActions.Audit to do this, but Service Center cannot give us all the information about this logs (I assume that is because of the size limit you referred).
What I actually need to know is how can we implement asynchronous logging in this situtation. Can you help me?
Thank you,
Ana Santos
Hello Ana, since this question is outside the scope of this thread, I took the liberty of opening a new thread with your question and replying to it. Please continue this discussion there.
I would like to know what is the memory size of each logs and where can I find it. Does logs with larger memory size affect my environment.
Regards,
Samuel Stephen
Hi Samuel,
I'm not sure I understand the purpose of your question. Low level memory management should not usually be a concern when developing with OutSystems.
You can look at the structure of the log tables to try and get an idea of how much memory they would take.
Logs are created and immediately placed in a queue which is usually rapidly flushed by the Log service. In a normal operating platform, these won't live long in memory so they are unlikely to affect your environment.
Or are you talking about the space they take up in the database?
Thank you Ricardo, it really helps alot.
Sachin, Rajat, do you really need to fully quote the entire post to say "thank you"? Please don't do that!
I refer to your statement
"The OutSystems Platform is capable of keeping logs for longer than they are displayed in Service Center. By default the OutSystems Platform keeps logs for 4 weeks, and can keep them for as long as 9 weeks. This is configurable in Configuration Tool, Logs tab [Windows] or Advanced Configuration Settings section [Linux]."
Is this feature available for cloud environments also if we raise a ticket with support?
For cloud environments, the logs are always set at the maximum and you cannot change this.
In order to get access to the underlying tables you need to use an extension or request direct access to the database.
Hello Team,
I could see some strange things in my database.
If am trying to truncate the OSLOG_ERROR table, it is getting truncated and it is again loading with the older logs only..
In this case, truncation is not working it seems.
Kindly do the needful ASAP.
Thanks in Advance..!!
Sripriya Sekar
Guys,
Checked the tables mentioned and indeed has the logs to up the current moment. However, my service center logs only shows up to only March 1 (as of posting March 14). What do I need to do?
JC Elorde wrote:
Run the configuration tool on the deployment controller and change the number of weeks retained.
J.Ja
Justin James wrote:
I have the same issue but on a cloud environment.
What can I do?
Thanks
Filipa
Hi Filipa,
You can contact OutSystems Support for this.
Hello,
When changing Log Cycle Period in Configuration Tool, is performing 'Create/Upgrade Database' needed?Or is only 'Apply and Exit' enough for this purpose?
And will this operation lead to interruption any application on my platform server?
Best regards.
Takasi Moriya wrote:
1. "Apply and exit" only.
2. It will probably ask you to restart the OutSystems services on the Deployment Controller, which is fine.
3. In the future, please start a new thread for a new question like this, and add to an existing thread if it is specific to the pre-existing conversation, thanks!
Hello Justin,
Thank you for replying kindly. I understood well.Sorry for using this thread for my question.