Repository navigation
docs(api): RUM query time range alignment and caching - #1131
Merged
Merged
Conversation
ysyneu
changed the title
ysyneu
marked this pull request as ready for review
October 26, 2026 10:12
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents how
/rum/data/queryand/rum/facet/countalign requested time ranges so repeated queries can reuse cached results.format=time_series: start rounded down and end rounded up to the bucket interval; bucket count and positions are unchanged.max(1 minute, range ÷ 1226 rounded up to the next interval step)when the range spans at least 100 such steps; shorter ranges are neither aligned nor cached.now()are neither aligned nor cached.Extended behavior is rendered through
x-mint.content; the operation subtitles remain concise.