fix(alerts): respect latest data for hourly trends alerts #39782
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.
Problem
Hourly trends alerts are not calculated properly.
For the cache key, we use relative dates (like
-2h
).We cache the trends value for the past hour using the relative date. Then, after 1 hour, for the next check, we use the cached value, which is not valid now.
Making the less expensive alerts calculations to ignore the caching, so they use the latest data, and prevent spamming alerts.
https://posthoghelp.zendesk.com/agent/tickets/39356
How did you test this code?
Manually + Added some tests