Splunk Search

Why does _time bucket give different results depending on how the data is sorted?

manus
Communicator

The following search returns two values (yesterday (1430780400) and today(1430866800)):
earliest=-d@d index=_internal
| bucket _time span=1d
| stats values(_time)

This search returns only one value (yesterday(1430780400)):
earliest=-d@d index=_internal
| sort _time
| bucket _time span=1d
| stats values(_time)

So sorting by _time affects the results of "bucket _time span=1d".
That looks like an undesired feature to me.

Tags (3)
0 Karma
1 Solution

HeinzWaescher
Motivator

How many events are searched for? I think the sort command you are using only uses 10k events.

Try this

 | sort 0 _time

View solution in original post

HeinzWaescher
Motivator

How many events are searched for? I think the sort command you are using only uses 10k events.

Try this

 | sort 0 _time

manus
Communicator

Thanks a lot, spot on. That was the problem. It's the second time I forget sort is constrained by default.

0 Karma
Get Updates on the Splunk Community!

Updated Team Landing Page in Splunk Observability

We’re making some changes to the team landing page in Splunk Observability, based on your feedback. The ...

New! Splunk Observability Search Enhancements for Splunk APM Services/Traces and ...

Regardless of where you are in Splunk Observability, you can search for relevant APM targets including service ...

Webinar Recap | Revolutionizing IT Operations: The Transformative Power of AI and ML ...

The Transformative Power of AI and ML in Enhancing Observability   In the realm of IT operations, the ...