Splunk Enterprise

Latency calculation in Splunk

VK18
Explorer

Hi Team,
I'm seeing following 22.77 as avg latency for the last 24 hours for one of the sourcetype. What is the normal avg latency that can be accepted since the logs are coming through syslog-> Heavy Forwarder->Indexer's and ingesting into splunk. 
Please let us know if there is any other alternative approach we can use to calculate the latency if below is incorrect.

VK18_1-1721631843112.png

 

Any help would be highly appreciated.

Regards
VK

 

Labels (1)
0 Karma
1 Solution

ITWhisperer
SplunkTrust
SplunkTrust

The calculation is correct for what it is. However, all this is is the difference between the time the event was indexed by Splunk and the timestamp Splunk has assigned to the event. This is usually based on the data in the event. Whether this represents "latency" is a matter of opinion and whether this is acceptable is also a matter of opinion. It very much depends on the route your data is taking and what the data represents. All of this is not something we can answer for you.

View solution in original post

ITWhisperer
SplunkTrust
SplunkTrust

The calculation is correct for what it is. However, all this is is the difference between the time the event was indexed by Splunk and the timestamp Splunk has assigned to the event. This is usually based on the data in the event. Whether this represents "latency" is a matter of opinion and whether this is acceptable is also a matter of opinion. It very much depends on the route your data is taking and what the data represents. All of this is not something we can answer for you.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...