Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(metric-stats): Use cardinality timestamp for reports #3626

Merged
merged 1 commit into from
May 21, 2024

Conversation

Dav1dde
Copy link
Member

@Dav1dde Dav1dde commented May 21, 2024

Aligns the timestamps of the cardinality reports with the actual cardinality limiting.

Without aligning the timestamps increased cardinality could spill over to new "metric minutes" which in general isn't a big problem but using the same timestamp is correct.

#skip-changelog

@Dav1dde Dav1dde requested a review from a team as a code owner May 21, 2024 06:18
@Dav1dde Dav1dde self-assigned this May 21, 2024
@Dav1dde Dav1dde mentioned this pull request May 21, 2024
@Dav1dde Dav1dde force-pushed the dav1d/timestamp-card-buckets branch from 819cc39 to d1beefe Compare May 21, 2024 06:21
@Dav1dde Dav1dde force-pushed the dav1d/timestamp-card-buckets branch from d1beefe to 29b4ff9 Compare May 21, 2024 06:43
@Dav1dde Dav1dde enabled auto-merge (squash) May 21, 2024 09:09
Copy link
Member

@jjbayer jjbayer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense, could you add a one-liner to the PR description about what can happen if these timestamps are not aligned?

@Dav1dde Dav1dde merged commit 692583e into master May 21, 2024
22 checks passed
@Dav1dde Dav1dde deleted the dav1d/timestamp-card-buckets branch May 21, 2024 09:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants