feat(ourlogs): Add auto-refresh to logs

[k-fish]

Summary

This adds an auto-refresh toggle behind the 'ourlogs-live-refresh' flag.

Auto-refresh can be enabled with filters so long as the sort is by time and descending. It works on 5 second polling, with a virtual time using RAF to emulate streaming. Filters are applied so data is queried in a ~30s second window behind our ingest delay.

Auto-refresh will automatically disable itself under the following conditions:

• You've hit a rate limit consistently over 3 polls (>1k logs/s)
• You've hit an api error for any reason
• You've hit the absolute timeout cap (10 minutes), you can re-enable it if you're actively using it
• You change sort / filter etc.

A subsequent PR will contain changes for the graph updates.

Other

• Added some memos and callbacks for performance reasons since the virtual timestamp updates fairly quickly
• Modified delayed data to follow already set delay in graphs (will be needed in the next PR)

[cursor]

Bug: Time-Based Sort Logic Incorrect

The checkSortIsTimeBasedDescending function contains incorrect logic. It checks if a time-based sort exists and if any sort in the array is descending, rather than specifically verifying that the time-based sort itself is descending. This can lead to the function returning true even when the time-based sort is ascending, as long as another field is sorted in descending order.

static/app/views/explore/logs/utils.tsx#L202-L208

sentry/static/app/views/explore/logs/utils.tsx

Lines 202 to 208 in cc21771

	export function checkSortIsTimeBasedDescending(sortBys: Sort[]) {
	return (
	getTimeBasedSortBy(sortBys) !== undefined &&
	sortBys.some(sortBy => sortBy.kind === 'desc')
	);
	}

Fix in Cursor • Fix in Web

---

Bug: Operator Precedence Error in Query Filters

Incorrect operator precedence in the expression (pageParam.querySortDirection ?? pageParam.sortByDirection === 'asc') causes it to evaluate as pageParam.querySortDirection ?? (pageParam.sortByDirection === 'asc'). Since pageParam.querySortDirection is a truthy object when present, this incorrectly forces the comparison operator to '>=', regardless of the actual sort direction, leading to malformed query filters.

static/app/views/explore/logs/useLogsQuery.tsx#L399-L401

sentry/static/app/views/explore/logs/useLogsQuery.tsx

Lines 399 to 401 in cc21771

	}
	const comparison =
	(pageParam.querySortDirection ?? pageParam.sortByDirection === 'asc') ? '>=' : '<=';

Fix in Cursor • Fix in Web

---

Bug: Delayed Data Marking Fails on Re-evaluation

The markDelayedData function prematurely returns if datum.incomplete is already defined. This prevents re-evaluation of data points against the current delay parameter, leading to incorrect incomplete statuses, especially when the delay value changes.

static/app/utils/timeSeries/markDelayedData.tsx#L25-L28

sentry/static/app/utils/timeSeries/markDelayedData.tsx

Lines 25 to 28 in cc21771

	if (defined(datum.incomplete)) {
	return datum;
	}

Fix in Cursor • Fix in Web

---

Was this report helpful? Give feedback by reacting with 👍 or 👎