Skip to content

fix: support {{period_start}} placeholder in Alert Insight#1341

Open
DdangJin wants to merge 1 commit intoopensearch-project:mainfrom
DdangJin:fix/alert-insight/period-start
Open

fix: support {{period_start}} placeholder in Alert Insight#1341
DdangJin wants to merge 1 commit intoopensearch-project:mainfrom
DdangJin:fix/alert-insight/period-start

Conversation

@DdangJin
Copy link
Copy Markdown

Description

Fixed an issue where Alert Insight failed to parse queries containing {{period_start}}.

The code has been updated to correctly calculate the start time (based on the notification time) and replace the {{period_start}} placeholder with the actual timestamp before executing the search.
This resolves the failed to parse date field exception when using time ranges in extraction queries.

Issues Resolved

Fixes #1340

Check List

  • New functionality includes testing.
    • All tests pass
  • New functionality has been documented.
    • New functionality has javadoc added
  • Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Signed-off-by: DdangJin <hdj997@gmail.com>
@DdangJin DdangJin force-pushed the fix/alert-insight/period-start branch from db7bbca to 5eaecdc Compare January 12, 2026 11:20
@DdangJin DdangJin changed the title [WIP] fix: support {{period_start}} placeholder in Alert Insight fix: support {{period_start}} placeholder in Alert Insight Jan 12, 2026
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.

[BUG] Alert Insight summary fails when extraction query contains {{period_start}}

1 participant