Splunk Search

Which regex is the correct extraction for Splunk EPOCH timestamp with decimal microseconds configuration in props.conf ?

baegoon
Explorer

I have timestamps in my data sources that are EPOCH with fractional microseconds for example:

1547528398.991103
1547528400.021926

I have set up my props.conf with the following:

INDEXED_EXTRACTIONS = TSV
TIME_FORMAT = %s.%6Q
KV_MODE = none
FIELD_DELIMITER = \t
FIELD_QUOTE = "
FIELD_NAMES = ts,hostid,tx_hosts,rx_hosts,conns,source,message
TIMESTAMP_FIELDS = ts
NO_BINARY_CHECK = true
SHOULD_LINEMERGE = false
TZ = UTC

I think the indexer is having a performance issue when processing the timestamps. However, I would like to know the following:

Is this the correct extraction for the EPOCH timestamp with microseconds? TIME_FORMAT = %s.%6Q or should the extraction be %s.%6N or some other format?

Can I tell Splunk in props.conf (or transforms.conf) to round the fractional seconds or drop them from processing?

Any help is appreciated!

Happy Splunking!

0 Karma

woodcock
Esteemed Legend

I have always used N instead of Q and have never had any problems. Either should be just fine, though.

Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Unlock What’s Next: The Splunk Cloud Platform at .conf25

In just a few days, Boston will be buzzing as the Splunk team and thousands of community members come together ...