You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a way to limit this, we are planning to set the "syslog_processing_thread_count":"4" to rectify the issue, but wanted to confirm if that is going to have some other side-effects that we should keep an eye on?
The text was updated successfully, but these errors were encountered:
@ManishJain-TomTom Before this change in 2.2.16 threads count was unlimited.
Setting syslog_processing_thread_count":"4" will limit the usage of memory by syslog monitor definitely, but if only it was really caused by syslog monitor.
Do you use syslog monitor in this agent configuration? Because if not, then modification of this parameter will not make any difference.
There could be something else behind the memory leak then.
We can open support ticket and troubleshoot memory leak if you would like to.
Hi Team,
We are using Scalyr in our K8s environment, and found that one of the scalyr agent is constantly using more and more memory.
We are using helm chart version 0.2.45 and scalyr version 2.2.16.
From the release logs of https://github.com/scalyr/scalyr-agent-2/releases/tag/v2.2.16, we saw the number of threads have been changed to 16. Could this be the reason for the increase in memory usage?
Is there a way to limit this, we are planning to set the
"syslog_processing_thread_count":"4"
to rectify the issue, but wanted to confirm if that is going to have some other side-effects that we should keep an eye on?The text was updated successfully, but these errors were encountered: