Splunk Search

Where to apply a time offset props when using a heavy forwarder

Runals
Motivator

I currently have a firewall whose time is set to GMT sending data into Splunk via a heavy forwarder. Since timestamps are extracted at the heavy forwarder (correct?) I deployed the props.conf to just there. My concern was if I put the props at both the HF and the indexers it would do the time diff type operation twice. However, when I look at those logs I see them in the future so to speak.

Of course as I write this I'm wondering if ultimately the indexers/heavy forwarders couldn't care less about the offset given they store the data in a 'native' format and this should be applied to the search heads.

Tags (1)
0 Karma

yannK
Splunk Employee
Splunk Employee

=> your condiguration seems correct.

The events and timestamp are parsed only once
This will happen on the HF, then the parsed events will be forwarded to the indexer, and it will write then directly to the buckets in the disk without parsing them a second time.

However, if you expected to setup any filtering/parsing/nullQueue routing on the indexer, it will not apply on the data from the HF.

0 Karma

Runals
Motivator

The problem is it isn't working =). To find the most recent events I have to set the time selector to the future

0 Karma
Get Updates on the Splunk Community!

Join Us for Splunk University and Get Your Bootcamp Game On!

If you know, you know! Splunk University is the vibe this summer so register today for bootcamps galore ...

.conf24 | Learning Tracks for Security, Observability, Platform, and Developers!

.conf24 is taking place at The Venetian in Las Vegas from June 11 - 14. Continue reading to learn about the ...

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...