Splunk Search

time range selection not working on CLI

glsplunk
New Member

I'm trying:

splunk search Calling -earliest=06/30/2014:11:40:00 AND -latest=06/30/2014:12:00:00

and i'm not getting results in that time range. I've tried adding _time to earliest and
latest, as I saw in the docs, nothing works. I've tried blanks instead of equal signs.

Tags (1)
0 Karma

Ayn
Legend

That's because CLI search doesn't use those options. They are called "earliest_time" and "latest_time", respectively.

http://docs.splunk.com/Documentation/Splunk/6.1.1/SearchReference/CLIsearchsyntax

0 Karma

glsplunk
New Member

yyyy-... doesn't work for me.
-earliest_time=06/30/2014 w/o hh:mm:ss isn't flagged as an
error, but the results include stuff from 06/27.
-earliest_time 2014/...
-earliest_time=2014-....
and such are called "invalid"

0 Karma

Ayn
Legend

Oh hm. When giving the time in the format you provided I'm getting an invalid format error. Try using YYYY-MM-DDTHH:MM:SS. For instance your earliest time would be "2014-06-30T11:40:00".

0 Karma

glsplunk
New Member

wrong.
like i said in the OP, i've tried adding _time to both
of those, and that doesn't work.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Note: This post outlines a proposed architecture and serves as an interest check. If we secure commitments ...