You might be able to do something like this:
base search | eval _time = strptime(date, "%Y%m%d%H%M%S") | timechart ...
However, do consider if it makes sense to use that date field as the actual _time
value when indexing future data.
You may want to try the chart command. "Unlike the timechart command which generates a chart with the _time field as the x-axis, the chart command produces a table with an arbitrary field as the x-axis."
Thanks for your suggestion martin. But it still taking _time on x-axis its not taking my time which is coming through eval _time = strptime(date, "%Y%m%d%H%M%S").
You might be able to do something like this:
base search | eval _time = strptime(date, "%Y%m%d%H%M%S") | timechart ...
However, do consider if it makes sense to use that date field as the actual _time
value when indexing future data.
When I run this over here:
index=_internal | head 1 | eval date="20140408045219" | eval _time = strptime(date, "%Y%m%d%H%M%S") | timechart count
I get a blip at 4:52AM rather than now (3:50PM).
It's still using the field called _time
, but with the value you've changed it to.