Getting Data In

What can cause an issue of a different time extraction over the same source type / log type?

mmoermans
Path Finder

Hi,

We've got a source type that extracts the date correctly (01/12/2018 in log, 01/12/2018 in Splunk). We've got a new host going to a new index with the same source type, but now the date is incorrect (01/12/2018 in log, 12/01/2018 in Splunk).

What can cause this issue of a different time extraction over the same sourcetype / log type?

0 Karma

ddrillic
Ultra Champion

For this specific sourcetype, did you specify explicitly the date/time extraction in props.conf?

0 Karma

whrg
Motivator

Which operating system is running on the new host?

My first thought is that the system language is different on the new host. Depending on the language, the date might get displayed/interpreted differently.

To demonstrate on CentOS:

# localectl
System Locale: LANG=en_US.UTF-8
# date +"%x"
12/05/2018

# localectl | grep Locale
System Locale: LANG=de_DE.utf8
# date +"%x"
05.12.2018
0 Karma
Get Updates on the Splunk Community!

.conf24 | Registration Open!

Hello, hello! I come bearing good news: Registration for .conf24 is now open!   conf is Splunk’s rad annual ...

Splunk is officially part of Cisco

Revolutionizing how our customers build resilience across their entire digital footprint.   Splunk ...

Splunk APM & RUM | Planned Maintenance March 26 - March 28, 2024

There will be planned maintenance for Splunk APM and RUM between March 26, 2024 and March 28, 2024 as ...