All Apps and Add-ons

Are there known issues with stream and HTTP persistent connections?

heath
Path Finder

We are trying to monitor response times of HTTP requests using stream using the time_taken value. When we enable HTTP persistent connections (aka http keep-alive, connection reuse or oneconnect in our f5 load balancer) and we run a load test, we notice that the time_taken reported by stream increases significantly and incorrectly. We can tell via other monitoring tools and packet captures that the time_taken is incorrect. Since the tcp connections get reused, it seems like it is mixing up which request belongs to which response and reporting longer times. Is this a known issue or are we missing something in our config?

Tags (1)
0 Karma
1 Solution

vshcherbakov_sp
Splunk Employee
Splunk Employee

Hello heath,

AFAIK, it's not a known issue. Would you be able to provide a sample capture file that exhibits the problem so that we can take a look at it?

Thanks in advance.

View solution in original post

0 Karma

vshcherbakov_sp
Splunk Employee
Splunk Employee

Hello heath,

AFAIK, it's not a known issue. Would you be able to provide a sample capture file that exhibits the problem so that we can take a look at it?

Thanks in advance.

0 Karma
Get Updates on the Splunk Community!

Splunk Forwarders and Forced Time Based Load Balancing

Splunk customers use universal forwarders to collect and send data to Splunk. A universal forwarder can send ...

NEW! Log Views in Splunk Observability Dashboards Gives Context From a Single Page

Today, Splunk Observability releases log views, a new feature for users to add their logs data from Splunk Log ...

Last Chance to Submit Your Paper For BSides Splunk - Deadline is August 12th!

Hello everyone! Don't wait to submit - The deadline is August 12th! We have truly missed the community so ...