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.

Get Updates on the Splunk Community!

Splunk Observability for AI

Don’t miss out on an exciting Tech Talk on Splunk Observability for AI!Discover how Splunk’s agentic AI ...

Splunk Enterprise Security 8.x: The Essential Upgrade for Threat Detection, ...

Watch On Demand the Tech Talk, and empower your SOC to reach new heights! Duration: 1 hour  Prepare to ...

Splunk Observability as Code: From Zero to Dashboard

For the details on what Self-Service Observability and Observability as Code is, we have some awesome content ...