Skip to content

fix: alerting time range filtering bug #814

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

Merged
merged 8 commits into from
May 16, 2025

Conversation

wrn14897
Copy link
Member

@wrn14897 wrn14897 commented May 14, 2025

Ref: HDX-1701

  1. fix alerting time range filtering
  2. add time range info to the alert body
image

Copy link

vercel bot commented May 14, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
hyperdx-v2-oss-app ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 16, 2025 5:42pm

Copy link

changeset-bot bot commented May 14, 2025

🦋 Changeset detected

Latest commit: c39ffeb

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

Comment on lines +688 to 693
{
ServiceName: 'api',
Timestamp: eventNextMs,
SeverityText: 'error',
Body: 'Oh no! Something went wrong!',
},
Copy link
Member Author

Choose a reason for hiding this comment

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

this new log line should test out the time boundary logic

@@ -716,6 +722,8 @@ export const processAlert = async (now: Date, alert: EnhancedAlert) => {
connection: connectionId,
displayType: DisplayType.Line,
dateRange: [checkStartTime, checkEndTime],
dateRangeStartInclusive: true,
dateRangeEndInclusive: false,
Copy link
Member Author

Choose a reason for hiding this comment

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

for alerts, we don't want to include the end of date range

Copy link

@knudtty knudtty left a comment

Choose a reason for hiding this comment

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

lgtm

@kodiakhq kodiakhq bot merged commit 321e24f into v2 May 16, 2025
6 of 7 checks passed
@kodiakhq kodiakhq bot deleted the warren/fix-alert-select-time-range-bug branch May 16, 2025 17:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants