Skip to content

[ML] Fixes today and this week filters for Log Rate / Pattern Analysis embeddables#252925

Merged
KodeRad merged 6 commits intoelastic:mainfrom
KodeRad:ml-log-pattern-analysis-fix
Feb 16, 2026
Merged

[ML] Fixes today and this week filters for Log Rate / Pattern Analysis embeddables#252925
KodeRad merged 6 commits intoelastic:mainfrom
KodeRad:ml-log-pattern-analysis-fix

Conversation

@KodeRad
Copy link
Contributor

@KodeRad KodeRad commented Feb 12, 2026 •
edited by kibanamachine
Loading

Summary

Fixes: #252909

Problem:
Dashboard time presets "Today" and "This week" send the same datemath string for both start and end (from: "now/d", to: "now/d" and from: "now/w", to: "now/w"). The AIOps embeddables were resolving these with datemath.parse() without roundUp for the end, so min and max were the same and the panels showed no results.

Fix:
Use the data plugin's calculateBounds (from @kbn/data-plugin/common) to resolve the time range in the embeddables, instead of manually calling datemath.parse(). calculateBounds always applies roundUp: true when parsing the end bound, which correctly resolves now/d to end-of-day and now/w to end-of-week. For absolute ISO date strings and ranges like now-24h to now, it returns the values unchanged since there is no rounding unit to apply. This is the same function used by the data plugin's createTimeRangeFilter (which powers Lens, Discover, and all other search requests), making the AIOps embeddables consistent with the rest of the platform.

Scope:
Log Rate Analysis and Log Pattern Analysis (Log Categorization) embeddables.

before after

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

  • Flaky Test Runner was used on any tests changed
  • The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines
  • Review the backport guidelines and apply applicable backport:* labels.

Identify risks

Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.
@KodeRad KodeRad force-pushed the ml-log-pattern-analysis-fix branch 2 times, most recently from 30b9bf3 to ee50bf0 Compare February 13, 2026 14:56
@elasticmachine
Copy link
Contributor

elasticmachine commented Feb 13, 2026 •
edited
Loading

⏳ Build in-progress, with failures

Failed CI Steps

History
@KodeRad KodeRad force-pushed the ml-log-pattern-analysis-fix branch from 564a201 to 6d7d264 Compare February 13, 2026 15:38
@KodeRad KodeRad self-assigned this Feb 13, 2026
@KodeRad KodeRad added bug Fixes for quality problems that affect the customer experience backport:version Backport to applied version labels v9.3.1 v9.4.0 release_note:fix :ml Team:ML Team label for ML (also use :ml) t// labels Feb 13, 2026
@KodeRad KodeRad marked this pull request as ready for review February 16, 2026 08:26
@KodeRad KodeRad requested a review from a team as a code owner February 16, 2026 08:26
@elasticmachine
Copy link
Contributor

elasticmachine commented Feb 16, 2026

Pinging @elastic/ml-ui (:ml)
@KodeRad KodeRad changed the title fix: today and this week filters for Log Rate / Pattern Analysis embe… Feb 16, 2026
@peteharverson peteharverson changed the title [ML] fix today and this week filters for Log Rate / Pattern Analysis embeddables Feb 16, 2026
jgowdyelastic
jgowdyelastic approved these changes Feb 16, 2026
View reviewed changes
Copy link
Member

@jgowdyelastic jgowdyelastic left a comment

Choose a reason for hiding this comment

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

Added a comment, but on the whole LGTM
peteharverson
peteharverson approved these changes Feb 16, 2026
View reviewed changes
Copy link
Contributor

@peteharverson peteharverson left a comment

Choose a reason for hiding this comment

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

Tested and LGTM
KodeRad and others added 2 commits February 16, 2026 15:28
@KodeRad @jgowdyelastic
Update x-pack/platform/plugins/shared/aiops/public/components/log_cat…
8d838d0 
…egorization/log_categorization_for_embeddable/log_categorization_for_embeddable.tsx

Co-authored-by: James Gowdy <jgowdy@elastic.co>
@KodeRad
Merge branch 'main' into ml-log-pattern-analysis-fix
15f4d17
@KodeRad KodeRad enabled auto-merge (squash) February 16, 2026 14:28
@KodeRad KodeRad merged commit 7aa3b78 into elastic:main Feb 16, 2026
16 checks passed
@kibanamachine
Copy link
Contributor

kibanamachine commented Feb 16, 2026

Starting backport for target branches: 9.3

https://github.com/elastic/kibana/actions/runs/22069419176
kibanamachine added a commit to kibanamachine/kibana that referenced this pull request Feb 16, 2026
@KodeRad @kibanamachine @jgowdyelastic
[ML] Fixes today and this week filters for Log Rate / Pattern Analysi…
4babbf0 
…s embeddables (elastic#252925)

## Summary

Fixes: elastic#252909

Problem:
Dashboard time presets "Today" and "This week" send the same datemath
string for both start and end (from: "now/d", to: "now/d" and from:
"now/w", to: "now/w"). The AIOps embeddables were resolving these with
`datemath.parse()` without `roundUp` for the end, so `min` and `max`
were the same and the panels showed no results.

Fix:
Use the data plugin's calculateBounds (from @kbn/data-plugin/common) to
resolve the time range in the embeddables, instead of manually calling
datemath.parse(). calculateBounds always applies roundUp: true when
parsing the end bound, which correctly resolves now/d to end-of-day and
now/w to end-of-week. For absolute ISO date strings and ranges like
now-24h to now, it returns the values unchanged since there is no
rounding unit to apply. This is the same function used by the data
plugin's createTimeRangeFilter (which powers Lens, Discover, and all
other search requests), making the AIOps embeddables consistent with the
rest of the platform.

Scope:
Log Rate Analysis and Log Pattern Analysis (Log Categorization)
embeddables.

<img width="1719" height="1009" alt="before"
src="https://github.com/user-attachments/assets/8c47ff66-3c69-4e2d-82ef-ab93abb3c598"
/>
<img width="1718" height="994" alt="after"
src="https://github.com/user-attachments/assets/023c5730-f976-4e9d-8aaf-2d7d4821b4a0"
/>

### Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- [x] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

### Identify risks

Does this PR introduce any risks? For example, consider risks like hard
to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified
risk. Invite stakeholders and evaluate how to proceed before merging.

- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
- [ ] ...

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: James Gowdy <jgowdy@elastic.co>
(cherry picked from commit 7aa3b78)
@kibanamachine kibanamachine mentioned this pull request Feb 16, 2026
Merged
@kibanamachine
Copy link
Contributor

kibanamachine commented Feb 16, 2026

💚 All backports created successfully

Status Branch Result
✅ 9.3

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation
kibanamachine added a commit that referenced this pull request Feb 17, 2026
@kibanamachine @KodeRad @jgowdyelastic
[9.3] [ML] Fixes today and this week filters for Log Rate / Pattern A…
8a9d951 
…nalysis embeddables (#252925) (#253310)

# Backport

This will backport the following commits from `main` to `9.3`:
- [[ML] Fixes today and this week filters for Log Rate / Pattern
Analysis embeddables
(#252925)](#252925)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Konrad
Krasocki","email":"104936644+KodeRad@users.noreply.github.com"},"sourceCommit":{"committedDate":"2026-02-16T15:54:38Z","message":"[ML]
Fixes today and this week filters for Log Rate / Pattern Analysis
embeddables (#252925)\n\n## Summary\n\nFixes:
https://github.com/elastic/kibana/issues/252909\n\nProblem:\nDashboard
time presets \"Today\" and \"This week\" send the same datemath\nstring
for both start and end (from: \"now/d\", to: \"now/d\" and
from:\n\"now/w\", to: \"now/w\"). The AIOps embeddables were resolving
these with\n`datemath.parse()` without `roundUp` for the end, so `min`
and `max`\nwere the same and the panels showed no results.\n\nFix: \nUse
the data plugin's calculateBounds (from @kbn/data-plugin/common)
to\nresolve the time range in the embeddables, instead of manually
calling\ndatemath.parse(). calculateBounds always applies roundUp: true
when\nparsing the end bound, which correctly resolves now/d to
end-of-day and\nnow/w to end-of-week. For absolute ISO date strings and
ranges like\nnow-24h to now, it returns the values unchanged since there
is no\nrounding unit to apply. This is the same function used by the
data\nplugin's createTimeRangeFilter (which powers Lens, Discover, and
all\nother search requests), making the AIOps embeddables consistent
with the\nrest of the platform.\n\nScope:\nLog Rate Analysis and Log
Pattern Analysis (Log Categorization)\nembeddables.\n\n<img
width=\"1719\" height=\"1009\"
alt=\"before\"\nsrc=\"https://github.com/user-attachments/assets/8c47ff66-3c69-4e2d-82ef-ab93abb3c598\"\n/>\n<img
width=\"1718\" height=\"994\"
alt=\"after\"\nsrc=\"https://github.com/user-attachments/assets/023c5730-f976-4e9d-8aaf-2d7d4821b4a0\"\n/>\n\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [x] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n-
[x] Review the
[backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand
apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this
PR introduce any risks? For example, consider risks like hard\nto test
bugs, performance regression, potential of data loss.\n\nDescribe the
risk, its severity, and mitigation for each identified\nrisk. Invite
stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See
some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ] ...\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: James
Gowdy
<jgowdy@elastic.co>","sha":"7aa3b7878786d2d48ea3ee772777a31fc911cb9f","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix",":ml","Team:ML","backport:version","v9.4.0","v9.3.1"],"title":"[ML]
Fixes today and this week filters for Log Rate / Pattern Analysis
embeddables","number":252925,"url":"https://github.com/elastic/kibana/pull/252925","mergeCommit":{"message":"[ML]
Fixes today and this week filters for Log Rate / Pattern Analysis
embeddables (#252925)\n\n## Summary\n\nFixes:
https://github.com/elastic/kibana/issues/252909\n\nProblem:\nDashboard
time presets \"Today\" and \"This week\" send the same datemath\nstring
for both start and end (from: \"now/d\", to: \"now/d\" and
from:\n\"now/w\", to: \"now/w\"). The AIOps embeddables were resolving
these with\n`datemath.parse()` without `roundUp` for the end, so `min`
and `max`\nwere the same and the panels showed no results.\n\nFix: \nUse
the data plugin's calculateBounds (from @kbn/data-plugin/common)
to\nresolve the time range in the embeddables, instead of manually
calling\ndatemath.parse(). calculateBounds always applies roundUp: true
when\nparsing the end bound, which correctly resolves now/d to
end-of-day and\nnow/w to end-of-week. For absolute ISO date strings and
ranges like\nnow-24h to now, it returns the values unchanged since there
is no\nrounding unit to apply. This is the same function used by the
data\nplugin's createTimeRangeFilter (which powers Lens, Discover, and
all\nother search requests), making the AIOps embeddables consistent
with the\nrest of the platform.\n\nScope:\nLog Rate Analysis and Log
Pattern Analysis (Log Categorization)\nembeddables.\n\n<img
width=\"1719\" height=\"1009\"
alt=\"before\"\nsrc=\"https://github.com/user-attachments/assets/8c47ff66-3c69-4e2d-82ef-ab93abb3c598\"\n/>\n<img
width=\"1718\" height=\"994\"
alt=\"after\"\nsrc=\"https://github.com/user-attachments/assets/023c5730-f976-4e9d-8aaf-2d7d4821b4a0\"\n/>\n\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [x] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n-
[x] Review the
[backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand
apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this
PR introduce any risks? For example, consider risks like hard\nto test
bugs, performance regression, potential of data loss.\n\nDescribe the
risk, its severity, and mitigation for each identified\nrisk. Invite
stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See
some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ] ...\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: James
Gowdy
<jgowdy@elastic.co>","sha":"7aa3b7878786d2d48ea3ee772777a31fc911cb9f"}},"sourceBranch":"main","suggestedTargetBranches":["9.3"],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/252925","number":252925,"mergeCommit":{"message":"[ML]
Fixes today and this week filters for Log Rate / Pattern Analysis
embeddables (#252925)\n\n## Summary\n\nFixes:
https://github.com/elastic/kibana/issues/252909\n\nProblem:\nDashboard
time presets \"Today\" and \"This week\" send the same datemath\nstring
for both start and end (from: \"now/d\", to: \"now/d\" and
from:\n\"now/w\", to: \"now/w\"). The AIOps embeddables were resolving
these with\n`datemath.parse()` without `roundUp` for the end, so `min`
and `max`\nwere the same and the panels showed no results.\n\nFix: \nUse
the data plugin's calculateBounds (from @kbn/data-plugin/common)
to\nresolve the time range in the embeddables, instead of manually
calling\ndatemath.parse(). calculateBounds always applies roundUp: true
when\nparsing the end bound, which correctly resolves now/d to
end-of-day and\nnow/w to end-of-week. For absolute ISO date strings and
ranges like\nnow-24h to now, it returns the values unchanged since there
is no\nrounding unit to apply. This is the same function used by the
data\nplugin's createTimeRangeFilter (which powers Lens, Discover, and
all\nother search requests), making the AIOps embeddables consistent
with the\nrest of the platform.\n\nScope:\nLog Rate Analysis and Log
Pattern Analysis (Log Categorization)\nembeddables.\n\n<img
width=\"1719\" height=\"1009\"
alt=\"before\"\nsrc=\"https://github.com/user-attachments/assets/8c47ff66-3c69-4e2d-82ef-ab93abb3c598\"\n/>\n<img
width=\"1718\" height=\"994\"
alt=\"after\"\nsrc=\"https://github.com/user-attachments/assets/023c5730-f976-4e9d-8aaf-2d7d4821b4a0\"\n/>\n\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [x] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n-
[x] Review the
[backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand
apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this
PR introduce any risks? For example, consider risks like hard\nto test
bugs, performance regression, potential of data loss.\n\nDescribe the
risk, its severity, and mitigation for each identified\nrisk. Invite
stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See
some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ] ...\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: James
Gowdy
<jgowdy@elastic.co>","sha":"7aa3b7878786d2d48ea3ee772777a31fc911cb9f"}},{"branch":"9.3","label":"v9.3.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Konrad Krasocki <104936644+KodeRad@users.noreply.github.com>
Co-authored-by: James Gowdy <jgowdy@elastic.co>
paulinashakirova pushed a commit to paulinashakirova/kibana that referenced this pull request Feb 17, 2026
@KodeRad @kibanamachine
@jgowdyelastic @paulinashakirova
[ML] Fixes today and this week filters for Log Rate / Pattern Analysi…
a95e9d4 
…s embeddables (elastic#252925)

## Summary

Fixes: elastic#252909

Problem:
Dashboard time presets "Today" and "This week" send the same datemath
string for both start and end (from: "now/d", to: "now/d" and from:
"now/w", to: "now/w"). The AIOps embeddables were resolving these with
`datemath.parse()` without `roundUp` for the end, so `min` and `max`
were the same and the panels showed no results.

Fix: 
Use the data plugin's calculateBounds (from @kbn/data-plugin/common) to
resolve the time range in the embeddables, instead of manually calling
datemath.parse(). calculateBounds always applies roundUp: true when
parsing the end bound, which correctly resolves now/d to end-of-day and
now/w to end-of-week. For absolute ISO date strings and ranges like
now-24h to now, it returns the values unchanged since there is no
rounding unit to apply. This is the same function used by the data
plugin's createTimeRangeFilter (which powers Lens, Discover, and all
other search requests), making the AIOps embeddables consistent with the
rest of the platform.

Scope:
Log Rate Analysis and Log Pattern Analysis (Log Categorization)
embeddables.

<img width="1719" height="1009" alt="before"
src="https://github.com/user-attachments/assets/8c47ff66-3c69-4e2d-82ef-ab93abb3c598"
/>
<img width="1718" height="994" alt="after"
src="https://github.com/user-attachments/assets/023c5730-f976-4e9d-8aaf-2d7d4821b4a0"
/>


### Checklist

Check the PR satisfies following conditions. 

Reviewers should verify this PR satisfies this list as well.

- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- [x] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

### Identify risks

Does this PR introduce any risks? For example, consider risks like hard
to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified
risk. Invite stakeholders and evaluate how to proceed before merging.

- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
- [ ] ...

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: James Gowdy <jgowdy@elastic.co>
patrykkopycinski pushed a commit to patrykkopycinski/kibana that referenced this pull request Feb 19, 2026
@KodeRad @kibanamachine
@jgowdyelastic @patrykkopycinski
[ML] Fixes today and this week filters for Log Rate / Pattern Analysi…
d11d7f4 
…s embeddables (elastic#252925)

## Summary

Fixes: elastic#252909

Problem:
Dashboard time presets "Today" and "This week" send the same datemath
string for both start and end (from: "now/d", to: "now/d" and from:
"now/w", to: "now/w"). The AIOps embeddables were resolving these with
`datemath.parse()` without `roundUp` for the end, so `min` and `max`
were the same and the panels showed no results.

Fix: 
Use the data plugin's calculateBounds (from @kbn/data-plugin/common) to
resolve the time range in the embeddables, instead of manually calling
datemath.parse(). calculateBounds always applies roundUp: true when
parsing the end bound, which correctly resolves now/d to end-of-day and
now/w to end-of-week. For absolute ISO date strings and ranges like
now-24h to now, it returns the values unchanged since there is no
rounding unit to apply. This is the same function used by the data
plugin's createTimeRangeFilter (which powers Lens, Discover, and all
other search requests), making the AIOps embeddables consistent with the
rest of the platform.

Scope:
Log Rate Analysis and Log Pattern Analysis (Log Categorization)
embeddables.

<img width="1719" height="1009" alt="before"
src="https://github.com/user-attachments/assets/8c47ff66-3c69-4e2d-82ef-ab93abb3c598"
/>
<img width="1718" height="994" alt="after"
src="https://github.com/user-attachments/assets/023c5730-f976-4e9d-8aaf-2d7d4821b4a0"
/>


### Checklist

Check the PR satisfies following conditions. 

Reviewers should verify this PR satisfies this list as well.

- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- [x] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

### Identify risks

Does this PR introduce any risks? For example, consider risks like hard
to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified
risk. Invite stakeholders and evaluate how to proceed before merging.

- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
- [ ] ...

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: James Gowdy <jgowdy@elastic.co>
ersin-erdal pushed a commit to ersin-erdal/kibana that referenced this pull request Feb 19, 2026
@KodeRad @kibanamachine
@jgowdyelastic @ersin-erdal
[ML] Fixes today and this week filters for Log Rate / Pattern Analysi…
fff658e 
…s embeddables (elastic#252925)

## Summary

Fixes: elastic#252909

Problem:
Dashboard time presets "Today" and "This week" send the same datemath
string for both start and end (from: "now/d", to: "now/d" and from:
"now/w", to: "now/w"). The AIOps embeddables were resolving these with
`datemath.parse()` without `roundUp` for the end, so `min` and `max`
were the same and the panels showed no results.

Fix: 
Use the data plugin's calculateBounds (from @kbn/data-plugin/common) to
resolve the time range in the embeddables, instead of manually calling
datemath.parse(). calculateBounds always applies roundUp: true when
parsing the end bound, which correctly resolves now/d to end-of-day and
now/w to end-of-week. For absolute ISO date strings and ranges like
now-24h to now, it returns the values unchanged since there is no
rounding unit to apply. This is the same function used by the data
plugin's createTimeRangeFilter (which powers Lens, Discover, and all
other search requests), making the AIOps embeddables consistent with the
rest of the platform.

Scope:
Log Rate Analysis and Log Pattern Analysis (Log Categorization)
embeddables.

<img width="1719" height="1009" alt="before"
src="https://github.com/user-attachments/assets/8c47ff66-3c69-4e2d-82ef-ab93abb3c598"
/>
<img width="1718" height="994" alt="after"
src="https://github.com/user-attachments/assets/023c5730-f976-4e9d-8aaf-2d7d4821b4a0"
/>


### Checklist

Check the PR satisfies following conditions. 

Reviewers should verify this PR satisfies this list as well.

- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- [x] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

### Identify risks

Does this PR introduce any risks? For example, consider risks like hard
to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified
risk. Invite stakeholders and evaluate how to proceed before merging.

- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
- [ ] ...

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: James Gowdy <jgowdy@elastic.co>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:version Backport to applied version labels bug Fixes for quality problems that affect the customer experience :ml release_note:fix Team:ML Team label for ML (also use :ml) t// v9.3.1 v9.4.0

5 participants

@KodeRad @elasticmachine @kibanamachine @peteharverson @jgowdyelastic