Getting Data In

Is there a solution (yet) for setting the TZ for a syslog host?

the_wolverine
Champion

If I recall correctly, there wasn't a way to set/offset the TZ for a syslog host. Has this changed?

Jason
Motivator

Could you not set the TZ at the [source::514] level? This would of course set the TZ for the entire syslog stream.

If we knew what key TZ= in props.conf sets, we could possibly write an index-time transform for it:

[tz_for_host1]
SOURCE_KEY = MetaData:Host
REGEX = host1
DEST_KEY = (whatever key TZ is)
FORMAT = The/Timezone
0 Karma

hazekamp
Builder

wolverine,

I believe this issue has to do with the order by which an event gets processed. The host extraction performed on syslog data at index time occurs after Splunk applies TZ properties. As a result, TZ properties applied on the extracted host field do not take affect. This is mostly a problem for syslog data that is not collected directly from the host which it originated.

Update:
I do not have a definitive solution/workaround. You could try routing the data through a full forwarder before you index; where the indexer input is set to "parsingQueue" for a second round of parsing.

0 Karma

the_wolverine
Champion

Thank you for your response, hazedev. I understand why it does not work. I'm wondering if a solution was provided recently. I recall there was a possible workaround for this.

0 Karma
Get Updates on the Splunk Community!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...