-
Notifications
You must be signed in to change notification settings - Fork 253
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
🦋 Changeset detectedLatest commit: c39ffeb The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
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 |
{ | ||
ServiceName: 'api', | ||
Timestamp: eventNextMs, | ||
SeverityText: 'error', | ||
Body: 'Oh no! Something went wrong!', | ||
}, |
There was a problem hiding this comment.
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, |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Ref: HDX-1701