Deployment Architecture

TIME_FORMAT on props.conf broke line breaking.

agodoy
Communicator

Hello,
I have timestamps in the following format.

1383058343.661030

I added the following to my props.conf.

TIME_FORMAT = %s%6N

This was in a Splunk cluster. After the bundle was applied, the events stopped breaking like they normally do. Instead they started to be grouped together.

Questions:

  1. Is the time format correct for the time stamp?
  2. Do I need to add other configs on the peer side to allow for proper line breaking.
0 Karma
1 Solution

kristian_kolb
Ultra Champion

You are missing the dot.

TIME_FORMAT = %s.%6N

/K

View solution in original post

0 Karma

kristian_kolb
Ultra Champion

You are missing the dot.

TIME_FORMAT = %s.%6N

/K

0 Karma

agodoy
Communicator

I did indeed. Thanks!

0 Karma

kristian_kolb
Ultra Champion

And yes, this configuration is supposed to go to the indexers (or to a Heavy Forwarder - whichever comes first)

http://wiki.splunk.com/Where_do_I_configure_my_Splunk_settings

/K

0 Karma
Get Updates on the Splunk Community!

Accelerating Observability as Code with the Splunk AI Assistant

We’ve seen in previous posts what Observability as Code (OaC) is and how it’s now essential for managing ...

Integrating Splunk Search API and Quarto to Create Reproducible Investigation ...

 Splunk is More Than Just the Web Console For Digital Forensics and Incident Response (DFIR) practitioners, ...

Congratulations to the 2025-2026 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...