feat: Align date ranges to chart and MV granularity (Line/Bar charts)

[pulpdrew]

Closes HDX-3067
Closes #1331
Closes #1212
Closes #1468

Summary

This PR makes a number of improvements around the way we handle date ranges and granularities, in an effort to minimize discrepancies between aggregate values queried from original data and aggregate values queried from materialized views.

1. Date ranges for Line and Bar chart queries are now (by default) auto-aligned to the chart's granularity. This is not limited to materialized view queries. Since the chart granularity is a multiple of the MV granularity, this ensures that the date range is aligned to the MV granularity as well. This also address a number of related issues that point out 0-values or low-values in the first or last data points. This PR also includes an option to disable this behavior for charts in Chart Explorer or Dashboard Tiles.
2. All materialized view queries and all time chart queries are now end-exclusive, to avoid selecting the entirety of the next "time bucket" from the materialized view when the date range is aligned with the materialized view granularity
3. Materialized views are only used for a query with a granularity if the chart query granularity is a multiple of the MV granularity. Previously, we'd use the MV as long as the chart query granularity was at least as large as the MV granularity, but this could cause unequal distributions of data across time buckets. Nearly all available granularities are multiples of all smaller available granularities - so this should only impact queries with granularity 15 minutes with MVs with granularity 10 minutes. 10m granularity support is being removed in chore: Standardize granularities #1551

Demo

Show Complete Intervals Option

Screen.Recording.2025-12-29.at.3.20.59.PM.mov

[changeset-bot]

🦋 Changeset detected

Latest commit: 4fd206b

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages

Name	Type
@hyperdx/common-utils	Patch
@hyperdx/api	Patch
@hyperdx/app	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
hyperdx-v2-oss-app	Ready	Preview, Comment	Jan 7, 2026 6:42pm

[claude]

Code Review

Critical Issues

• Previous period offset calculation bug at DBTimeChart.tsx:287-290 uses aligned date ranges instead of original ranges, causing incorrect offsets when alignment changes boundaries. Fix: use differenceInSeconds(originalDateRange[1], originalDateRange[0])

Important Issues

• Missing null safety at ChartUtils.tsx:169-171 where getAlignedDateRange receives granularity that could still be 'auto' from line 163-166. Add type guard.

Quality Issues

• getAlignedDateRange tests miss edge cases: DST transitions, leap seconds, year boundaries
• DBSearchPage.tsx:1370 alignment logic using !isLive is correct but unintuitive - add comment explaining cache behavior

Non-Blocking

• materializedViews.ts:158 modulo check is good but lacks comment on why 15min/10min fails

Recommendation: Fix offset calculation bug before merge

[github-actions]

E2E Test Results

✅ All tests passed • 56 passed • 4 skipped • 710s

Status	Count
✅ Passed	56
❌ Failed	0
⚠️ Flaky	0
⏭️ Skipped	4

Tests ran across 4 shards in parallel.

View full report →

[knudtty]

Long awaited! Great fix