You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Histogram event count doesn't match table row count for small time ranges #2255
When selecting a very small time range in the search page (e.g. 2 seconds: 13:29:54 ~ 13:29:56), the histogram displays a total count (e.g. 39) that doesn't match the number of rows shown in the results table (e.g. 3).
Steps to reproduce
Open the Search page
Select a very short custom time range (e.g. 2 seconds)
Observe the histogram total count vs. the number of rows in the table
Expected behavior
The histogram count and the table row count should reflect the same time window and show the same number of events.
Actual behavior
The histogram shows a larger count than the table rows. For example, querying 13:29:54 ~ 13:29:56 shows 39 events in the histogram but only 3 rows in the table.
Root cause
The auto-detected granularity has a minimum of 15 seconds. For any time range shorter than ~1200 seconds, the granularity resolves to 15 second. When the histogram date range is aligned to the nearest 15-second interval boundaries, the query window expands from the user's 2-second selection to a full 15-second window (e.g. 13:29:45 ~ 13:30:00).
Activity
brandon-pereira commentedon May 11, 2026
Good find - can confirm on my end as well. Please feel free to open a fix if you are able 😄
fix: Ensure search histogram count matches result table count (#2256)