Getting Data In

How do I deal w. single digit months/days in vix.input.1.et.regex?

jimjh
Path Finder

I have directory paths that look like

/year=2014/month=6/day=4/hour=1/

However, using the following regex is suboptimal, because yyyyMdH can cause ambiguity:

vix.input.1.et.regex = /year=(\d+)/month=(\d+)/day=(\d+)/hour=(\d+)/
vix.input.1.et.format = yyyyMdH

For example, given /year=2014/month=7/day=15/hour=9, Hunk will extract the digits, concatenate them into a string, and try to parse it as such:

scala> new SimpleDateFormat("yyyyMdH").parse("20147159")
res0: java.util.Date = Thu Jul 03 11:00:00 PDT 2014

which is incorrect. What regex should I use in this case?

Tags (2)
0 Karma
1 Solution

jimjh
Path Finder

Moving the = symbol into the capturing groups allows you to remove any ambiguity.

 vix.input.1.et.regex = /year(=\d+)/month(=\d+)/day(=\d+)/hour(=\d+)/
 vix.input.1.et.format = =yyyy=M=d=H

View solution in original post

jimjh
Path Finder

Moving the = symbol into the capturing groups allows you to remove any ambiguity.

 vix.input.1.et.regex = /year(=\d+)/month(=\d+)/day(=\d+)/hour(=\d+)/
 vix.input.1.et.format = =yyyy=M=d=H
Get Updates on the Splunk Community!

Index This | What is broken 80% of the time by February?

December 2025 Edition   Hayyy Splunk Education Enthusiasts and the Eternally Curious!    We’re back with this ...

Unlock Faster Time-to-Value on Edge and Ingest Processor with New SPL2 Pipeline ...

Hello Splunk Community,   We're thrilled to share an exciting update that will help you manage your data more ...

Splunk MCP & Agentic AI: Machine Data Without Limits

Discover how the Splunk Model Context Protocol (MCP) Server can revolutionize the way your organization uses ...