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
In HttpEventCollectorSender.java we would like to be able to configure desired number of http client connections as the default max of 2 connections for parallel mode is not sufficient for our throughput requirement.
The current default configuration causes too many requests to queue up (even with batching turned on) in case of any slowness on Splunk server. Having too many queued requests causes GC overhead and starts affecting business transactions. We use LogbackAppender to log events to splunk and any slowness in logging can potentially affect application performance.
The text was updated successfully, but these errors were encountered:
In HttpEventCollectorSender.java we would like to be able to configure desired number of http client connections as the default max of 2 connections for parallel mode is not sufficient for our throughput requirement.
The current default configuration causes too many requests to queue up (even with batching turned on) in case of any slowness on Splunk server. Having too many queued requests causes GC overhead and starts affecting business transactions. We use LogbackAppender to log events to splunk and any slowness in logging can potentially affect application performance.
The text was updated successfully, but these errors were encountered: