Skip to content

[ML] Anomaly Explorer: Fixes display of alerts from anomaly detection alerting rule#236289

Merged
rbrtj merged 2 commits intoelastic:mainfrom
rbrtj:update-ml-alerting-consumers
Sep 26, 2025
Merged

[ML] Anomaly Explorer: Fixes display of alerts from anomaly detection alerting rule#236289
rbrtj merged 2 commits intoelastic:mainfrom
rbrtj:update-ml-alerting-consumers

Conversation

@rbrtj
Copy link
Contributor

@rbrtj rbrtj commented Sep 24, 2025 •
edited by kibanamachine
Loading

Resolves #235504
Currently, when an ML-only user creates ML rules from both creation flows, the consumer is set to alerts.
Creating a rule from the "Anomaly Detection Jobs" page in Stack management sets the consumer to stackAlerts for a user with access to both feature privileges, instead of setting the consumer to alerts.
With this PR, ML-only user will be able to access all ML rules, no matter if the consumer is alerts or stackAlerts.

Screenshot 2025-09-25 at 13 42 19
@rbrtj rbrtj self-assigned this Sep 24, 2025
@rbrtj rbrtj added release_note:fix :ml Team:ML Team label for ML (also use :ml) t// backport:version Backport to applied version labels v9.2.0 v8.18.8 v8.19.5 v9.0.8 v9.1.5 labels Sep 24, 2025
@rbrtj rbrtj requested a review from peteharverson September 24, 2025 12:04
@rbrtj rbrtj marked this pull request as ready for review September 24, 2025 12:04
@rbrtj rbrtj requested a review from a team as a code owner September 24, 2025 12:04
@elasticmachine
Copy link
Contributor

elasticmachine commented Sep 24, 2025

Pinging @elastic/ml-ui (:ml)
@elasticmachine
Copy link
Contributor

elasticmachine commented Sep 25, 2025

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

  • [job] [logs] FTR Configs #72 / Space awareness enrollment_settings With Fleet server setup in a specific space "after all" hook in "With Fleet server setup in a specific space"

Metrics [docs]

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id before after diff
ml 86.2KB 86.3KB +36.0B

History

cc @rbrtj
@peteharverson peteharverson changed the title [ML] Alerting: Update consumers so ML users can view all created ML rules Sep 25, 2025
peteharverson
peteharverson approved these changes Sep 25, 2025
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. Confirmed that alerts from anomaly detection alerting rules which have "consumer": "stackAlerts" are now displayed in the Anomaly Explorer along with ones where "consumer": "alerts". Before this fix, only ones with "consumer": "alerts" were displayed.
@rbrtj rbrtj merged commit 7d682e3 into elastic:main Sep 26, 2025
12 checks passed
@kibanamachine
Copy link
Contributor

kibanamachine commented Sep 26, 2025

Starting backport for target branches: 8.18, 8.19, 9.0, 9.1

https://github.com/elastic/kibana/actions/runs/18036768438
kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Sep 26, 2025
@rbrtj
[ML] Anomaly Explorer: Fixes display of alerts from anomaly detection…
46411eb 
… alerting rule (elastic#236289)

Resolves elastic#235504
Currently, when an ML-only user creates ML rules from both creation
flows, the consumer is set to `alerts`.
Creating a rule from the "Anomaly Detection Jobs" page in Stack
management sets the consumer to `stackAlerts` for a user with access to
both feature privileges, instead of setting the consumer to `alerts`.
With this PR, ML-only user will be able to access all ML rules, no
matter if the consumer is `alerts` or `stackAlerts`.

<img width="896" height="611" alt="Screenshot 2025-09-25 at 13 42 19"
src="https://github.com/user-attachments/assets/14ec0af4-03fb-41e2-b3cf-de36106ed68c"
/>

(cherry picked from commit 7d682e3)
@kibanamachine kibanamachine mentioned this pull request Sep 26, 2025
Merged
kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Sep 26, 2025
@rbrtj
[ML] Anomaly Explorer: Fixes display of alerts from anomaly detection…
bf96c2e 
… alerting rule (elastic#236289)

Resolves elastic#235504
Currently, when an ML-only user creates ML rules from both creation
flows, the consumer is set to `alerts`.
Creating a rule from the "Anomaly Detection Jobs" page in Stack
management sets the consumer to `stackAlerts` for a user with access to
both feature privileges, instead of setting the consumer to `alerts`.
With this PR, ML-only user will be able to access all ML rules, no
matter if the consumer is `alerts` or `stackAlerts`.

<img width="896" height="611" alt="Screenshot 2025-09-25 at 13 42 19"
src="https://github.com/user-attachments/assets/14ec0af4-03fb-41e2-b3cf-de36106ed68c"
/>

(cherry picked from commit 7d682e3)
@kibanamachine kibanamachine mentioned this pull request Sep 26, 2025
Merged
@kibanamachine
Copy link
Contributor

kibanamachine commented Sep 26, 2025

💔 Some backports could not be created

Status Branch Result
❌ 8.18 Backport failed because of merge conflicts
✅ 8.19
❌ 9.0 Backport failed because of merge conflicts
✅ 9.1

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

Manual backport

To create the backport manually run:

node scripts/backport --pr 236289

Questions ?

Please refer to the Backport tool documentation
@rbrtj rbrtj mentioned this pull request Sep 26, 2025
Merged
rbrtj added a commit to rbrtj/kibana that referenced this pull request Sep 26, 2025
@rbrtj
[ML] Anomaly Explorer: Fixes display of alerts from anomaly detection…
9d17cfb 
… alerting rule (elastic#236289)

Resolves elastic#235504
Currently, when an ML-only user creates ML rules from both creation
flows, the consumer is set to `alerts`.
Creating a rule from the "Anomaly Detection Jobs" page in Stack
management sets the consumer to `stackAlerts` for a user with access to
both feature privileges, instead of setting the consumer to `alerts`.
With this PR, ML-only user will be able to access all ML rules, no
matter if the consumer is `alerts` or `stackAlerts`.

<img width="896" height="611" alt="Screenshot 2025-09-25 at 13 42 19"
src="https://github.com/user-attachments/assets/14ec0af4-03fb-41e2-b3cf-de36106ed68c"
/>

(cherry picked from commit 7d682e3)

# Conflicts:
#	x-pack/platform/plugins/shared/ml/common/types/capabilities.ts
@rbrtj rbrtj mentioned this pull request Sep 26, 2025
Merged
@rbrtj
Copy link
Contributor Author

rbrtj commented Sep 26, 2025

💚 All backports created successfully

Status Branch Result
✅ 9.0
✅ 8.18

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

Questions ?

Please refer to the Backport tool documentation
rbrtj added a commit to rbrtj/kibana that referenced this pull request Sep 26, 2025
@rbrtj
[ML] Anomaly Explorer: Fixes display of alerts from anomaly detection…
6433a19 
… alerting rule (elastic#236289)

Resolves elastic#235504
Currently, when an ML-only user creates ML rules from both creation
flows, the consumer is set to `alerts`.
Creating a rule from the "Anomaly Detection Jobs" page in Stack
management sets the consumer to `stackAlerts` for a user with access to
both feature privileges, instead of setting the consumer to `alerts`.
With this PR, ML-only user will be able to access all ML rules, no
matter if the consumer is `alerts` or `stackAlerts`.

<img width="896" height="611" alt="Screenshot 2025-09-25 at 13 42 19"
src="https://github.com/user-attachments/assets/14ec0af4-03fb-41e2-b3cf-de36106ed68c"
/>

(cherry picked from commit 7d682e3)

# Conflicts:
#	x-pack/platform/plugins/shared/ml/common/types/capabilities.ts
kibanamachine added a commit that referenced this pull request Sep 26, 2025
@kibanamachine @rbrtj
[9.1] [ML] Anomaly Explorer: Fixes display of alerts from anomaly det…
bba7f2d 
…ection alerting rule (#236289) (#236578)

# Backport

This will backport the following commits from `main` to `9.1`:
- [[ML] Anomaly Explorer: Fixes display of alerts from anomaly detection
alerting rule (#236289)](#236289)

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

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

<!--BACKPORT [{"author":{"name":"Robert
Jaszczurek","email":"92210485+rbrtj@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-09-26T11:43:40Z","message":"[ML]
Anomaly Explorer: Fixes display of alerts from anomaly detection
alerting rule (#236289)\n\nResolves
https://github.com/elastic/kibana/issues/235504\nCurrently, when an
ML-only user creates ML rules from both creation\nflows, the consumer is
set to `alerts`.\nCreating a rule from the \"Anomaly Detection Jobs\"
page in Stack\nmanagement sets the consumer to `stackAlerts` for a user
with access to\nboth feature privileges, instead of setting the consumer
to `alerts`.\nWith this PR, ML-only user will be able to access all ML
rules, no\nmatter if the consumer is `alerts` or `stackAlerts`.\n\n<img
width=\"896\" height=\"611\" alt=\"Screenshot 2025-09-25 at 13 42
19\"\nsrc=\"https://github.com/user-attachments/assets/14ec0af4-03fb-41e2-b3cf-de36106ed68c\"\n/>","sha":"7d682e38784717604aac8714ff9b7fd94dc3cac6","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Team:ML","backport:version","v9.2.0","v8.18.8","v8.19.5","v9.0.8","v9.1.5"],"title":"[ML]
Anomaly Explorer: Fixes display of alerts from anomaly detection
alerting
rule","number":236289,"url":"https://github.com/elastic/kibana/pull/236289","mergeCommit":{"message":"[ML]
Anomaly Explorer: Fixes display of alerts from anomaly detection
alerting rule (#236289)\n\nResolves
https://github.com/elastic/kibana/issues/235504\nCurrently, when an
ML-only user creates ML rules from both creation\nflows, the consumer is
set to `alerts`.\nCreating a rule from the \"Anomaly Detection Jobs\"
page in Stack\nmanagement sets the consumer to `stackAlerts` for a user
with access to\nboth feature privileges, instead of setting the consumer
to `alerts`.\nWith this PR, ML-only user will be able to access all ML
rules, no\nmatter if the consumer is `alerts` or `stackAlerts`.\n\n<img
width=\"896\" height=\"611\" alt=\"Screenshot 2025-09-25 at 13 42
19\"\nsrc=\"https://github.com/user-attachments/assets/14ec0af4-03fb-41e2-b3cf-de36106ed68c\"\n/>","sha":"7d682e38784717604aac8714ff9b7fd94dc3cac6"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.19","9.0","9.1"],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/236289","number":236289,"mergeCommit":{"message":"[ML]
Anomaly Explorer: Fixes display of alerts from anomaly detection
alerting rule (#236289)\n\nResolves
https://github.com/elastic/kibana/issues/235504\nCurrently, when an
ML-only user creates ML rules from both creation\nflows, the consumer is
set to `alerts`.\nCreating a rule from the \"Anomaly Detection Jobs\"
page in Stack\nmanagement sets the consumer to `stackAlerts` for a user
with access to\nboth feature privileges, instead of setting the consumer
to `alerts`.\nWith this PR, ML-only user will be able to access all ML
rules, no\nmatter if the consumer is `alerts` or `stackAlerts`.\n\n<img
width=\"896\" height=\"611\" alt=\"Screenshot 2025-09-25 at 13 42
19\"\nsrc=\"https://github.com/user-attachments/assets/14ec0af4-03fb-41e2-b3cf-de36106ed68c\"\n/>","sha":"7d682e38784717604aac8714ff9b7fd94dc3cac6"}},{"branch":"8.18","label":"v8.18.8","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.8","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.1","label":"v9.1.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Robert Jaszczurek <92210485+rbrtj@users.noreply.github.com>
kibanamachine added a commit that referenced this pull request Sep 26, 2025
@kibanamachine @rbrtj
[8.19] [ML] Anomaly Explorer: Fixes display of alerts from anomaly de…
0a47f48 
…tection alerting rule (#236289) (#236577)

# Backport

This will backport the following commits from `main` to `8.19`:
- [[ML] Anomaly Explorer: Fixes display of alerts from anomaly detection
alerting rule (#236289)](#236289)

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

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

<!--BACKPORT [{"author":{"name":"Robert
Jaszczurek","email":"92210485+rbrtj@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-09-26T11:43:40Z","message":"[ML]
Anomaly Explorer: Fixes display of alerts from anomaly detection
alerting rule (#236289)\n\nResolves
https://github.com/elastic/kibana/issues/235504\nCurrently, when an
ML-only user creates ML rules from both creation\nflows, the consumer is
set to `alerts`.\nCreating a rule from the \"Anomaly Detection Jobs\"
page in Stack\nmanagement sets the consumer to `stackAlerts` for a user
with access to\nboth feature privileges, instead of setting the consumer
to `alerts`.\nWith this PR, ML-only user will be able to access all ML
rules, no\nmatter if the consumer is `alerts` or `stackAlerts`.\n\n<img
width=\"896\" height=\"611\" alt=\"Screenshot 2025-09-25 at 13 42
19\"\nsrc=\"https://github.com/user-attachments/assets/14ec0af4-03fb-41e2-b3cf-de36106ed68c\"\n/>","sha":"7d682e38784717604aac8714ff9b7fd94dc3cac6","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Team:ML","backport:version","v9.2.0","v8.18.8","v8.19.5","v9.0.8","v9.1.5"],"title":"[ML]
Anomaly Explorer: Fixes display of alerts from anomaly detection
alerting
rule","number":236289,"url":"https://github.com/elastic/kibana/pull/236289","mergeCommit":{"message":"[ML]
Anomaly Explorer: Fixes display of alerts from anomaly detection
alerting rule (#236289)\n\nResolves
https://github.com/elastic/kibana/issues/235504\nCurrently, when an
ML-only user creates ML rules from both creation\nflows, the consumer is
set to `alerts`.\nCreating a rule from the \"Anomaly Detection Jobs\"
page in Stack\nmanagement sets the consumer to `stackAlerts` for a user
with access to\nboth feature privileges, instead of setting the consumer
to `alerts`.\nWith this PR, ML-only user will be able to access all ML
rules, no\nmatter if the consumer is `alerts` or `stackAlerts`.\n\n<img
width=\"896\" height=\"611\" alt=\"Screenshot 2025-09-25 at 13 42
19\"\nsrc=\"https://github.com/user-attachments/assets/14ec0af4-03fb-41e2-b3cf-de36106ed68c\"\n/>","sha":"7d682e38784717604aac8714ff9b7fd94dc3cac6"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.19","9.0","9.1"],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/236289","number":236289,"mergeCommit":{"message":"[ML]
Anomaly Explorer: Fixes display of alerts from anomaly detection
alerting rule (#236289)\n\nResolves
https://github.com/elastic/kibana/issues/235504\nCurrently, when an
ML-only user creates ML rules from both creation\nflows, the consumer is
set to `alerts`.\nCreating a rule from the \"Anomaly Detection Jobs\"
page in Stack\nmanagement sets the consumer to `stackAlerts` for a user
with access to\nboth feature privileges, instead of setting the consumer
to `alerts`.\nWith this PR, ML-only user will be able to access all ML
rules, no\nmatter if the consumer is `alerts` or `stackAlerts`.\n\n<img
width=\"896\" height=\"611\" alt=\"Screenshot 2025-09-25 at 13 42
19\"\nsrc=\"https://github.com/user-attachments/assets/14ec0af4-03fb-41e2-b3cf-de36106ed68c\"\n/>","sha":"7d682e38784717604aac8714ff9b7fd94dc3cac6"}},{"branch":"8.18","label":"v8.18.8","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.8","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.1","label":"v9.1.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Robert Jaszczurek <92210485+rbrtj@users.noreply.github.com>
rbrtj added a commit that referenced this pull request Sep 29, 2025
@rbrtj @kibanamachine
[8.18] [ML] Anomaly Explorer: Fixes display of alerts from anomaly de…
e1dae84 
…tection alerting rule (#236289) (#236605)

# Backport

This will backport the following commits from `main` to `8.18`:
- [[ML] Anomaly Explorer: Fixes display of alerts from anomaly detection
alerting rule (#236289)](#236289)

<!--- Backport version: 10.0.2 -->

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

<!--BACKPORT [{"author":{"name":"Robert
Jaszczurek","email":"92210485+rbrtj@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-09-26T11:43:40Z","message":"[ML]
Anomaly Explorer: Fixes display of alerts from anomaly detection
alerting rule (#236289)\n\nResolves
https://github.com/elastic/kibana/issues/235504\nCurrently, when an
ML-only user creates ML rules from both creation\nflows, the consumer is
set to `alerts`.\nCreating a rule from the \"Anomaly Detection Jobs\"
page in Stack\nmanagement sets the consumer to `stackAlerts` for a user
with access to\nboth feature privileges, instead of setting the consumer
to `alerts`.\nWith this PR, ML-only user will be able to access all ML
rules, no\nmatter if the consumer is `alerts` or `stackAlerts`.\n\n<img
width=\"896\" height=\"611\" alt=\"Screenshot 2025-09-25 at 13 42
19\"\nsrc=\"https://github.com/user-attachments/assets/14ec0af4-03fb-41e2-b3cf-de36106ed68c\"\n/>","sha":"7d682e38784717604aac8714ff9b7fd94dc3cac6","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Team:ML","backport:version","v9.2.0","v8.18.8","v8.19.5","v9.0.8","v9.1.5"],"title":"[ML]
Anomaly Explorer: Fixes display of alerts from anomaly detection
alerting
rule","number":236289,"url":"https://github.com/elastic/kibana/pull/236289","mergeCommit":{"message":"[ML]
Anomaly Explorer: Fixes display of alerts from anomaly detection
alerting rule (#236289)\n\nResolves
https://github.com/elastic/kibana/issues/235504\nCurrently, when an
ML-only user creates ML rules from both creation\nflows, the consumer is
set to `alerts`.\nCreating a rule from the \"Anomaly Detection Jobs\"
page in Stack\nmanagement sets the consumer to `stackAlerts` for a user
with access to\nboth feature privileges, instead of setting the consumer
to `alerts`.\nWith this PR, ML-only user will be able to access all ML
rules, no\nmatter if the consumer is `alerts` or `stackAlerts`.\n\n<img
width=\"896\" height=\"611\" alt=\"Screenshot 2025-09-25 at 13 42
19\"\nsrc=\"https://github.com/user-attachments/assets/14ec0af4-03fb-41e2-b3cf-de36106ed68c\"\n/>","sha":"7d682e38784717604aac8714ff9b7fd94dc3cac6"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/236289","number":236289,"mergeCommit":{"message":"[ML]
Anomaly Explorer: Fixes display of alerts from anomaly detection
alerting rule (#236289)\n\nResolves
https://github.com/elastic/kibana/issues/235504\nCurrently, when an
ML-only user creates ML rules from both creation\nflows, the consumer is
set to `alerts`.\nCreating a rule from the \"Anomaly Detection Jobs\"
page in Stack\nmanagement sets the consumer to `stackAlerts` for a user
with access to\nboth feature privileges, instead of setting the consumer
to `alerts`.\nWith this PR, ML-only user will be able to access all ML
rules, no\nmatter if the consumer is `alerts` or `stackAlerts`.\n\n<img
width=\"896\" height=\"611\" alt=\"Screenshot 2025-09-25 at 13 42
19\"\nsrc=\"https://github.com/user-attachments/assets/14ec0af4-03fb-41e2-b3cf-de36106ed68c\"\n/>","sha":"7d682e38784717604aac8714ff9b7fd94dc3cac6"}},{"branch":"8.18","label":"v8.18.8","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/236577","number":236577,"state":"OPEN"},{"branch":"9.0","label":"v9.0.8","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.1","label":"v9.1.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/236578","number":236578,"state":"OPEN"}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
rbrtj added a commit that referenced this pull request Sep 29, 2025
@rbrtj
[9.0] [ML] Anomaly Explorer: Fixes display of alerts from anomaly det…
7c282f2 
…ection alerting rule (#236289) (#236604)

# Backport

This will backport the following commits from `main` to `9.0`:
- [[ML] Anomaly Explorer: Fixes display of alerts from anomaly detection
alerting rule (#236289)](#236289)

<!--- Backport version: 10.0.2 -->

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

<!--BACKPORT [{"author":{"name":"Robert
Jaszczurek","email":"92210485+rbrtj@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-09-26T11:43:40Z","message":"[ML]
Anomaly Explorer: Fixes display of alerts from anomaly detection
alerting rule (#236289)\n\nResolves
https://github.com/elastic/kibana/issues/235504\nCurrently, when an
ML-only user creates ML rules from both creation\nflows, the consumer is
set to `alerts`.\nCreating a rule from the \"Anomaly Detection Jobs\"
page in Stack\nmanagement sets the consumer to `stackAlerts` for a user
with access to\nboth feature privileges, instead of setting the consumer
to `alerts`.\nWith this PR, ML-only user will be able to access all ML
rules, no\nmatter if the consumer is `alerts` or `stackAlerts`.\n\n<img
width=\"896\" height=\"611\" alt=\"Screenshot 2025-09-25 at 13 42
19\"\nsrc=\"https://github.com/user-attachments/assets/14ec0af4-03fb-41e2-b3cf-de36106ed68c\"\n/>","sha":"7d682e38784717604aac8714ff9b7fd94dc3cac6","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Team:ML","backport:version","v9.2.0","v8.18.8","v8.19.5","v9.0.8","v9.1.5"],"title":"[ML]
Anomaly Explorer: Fixes display of alerts from anomaly detection
alerting
rule","number":236289,"url":"https://github.com/elastic/kibana/pull/236289","mergeCommit":{"message":"[ML]
Anomaly Explorer: Fixes display of alerts from anomaly detection
alerting rule (#236289)\n\nResolves
https://github.com/elastic/kibana/issues/235504\nCurrently, when an
ML-only user creates ML rules from both creation\nflows, the consumer is
set to `alerts`.\nCreating a rule from the \"Anomaly Detection Jobs\"
page in Stack\nmanagement sets the consumer to `stackAlerts` for a user
with access to\nboth feature privileges, instead of setting the consumer
to `alerts`.\nWith this PR, ML-only user will be able to access all ML
rules, no\nmatter if the consumer is `alerts` or `stackAlerts`.\n\n<img
width=\"896\" height=\"611\" alt=\"Screenshot 2025-09-25 at 13 42
19\"\nsrc=\"https://github.com/user-attachments/assets/14ec0af4-03fb-41e2-b3cf-de36106ed68c\"\n/>","sha":"7d682e38784717604aac8714ff9b7fd94dc3cac6"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/236289","number":236289,"mergeCommit":{"message":"[ML]
Anomaly Explorer: Fixes display of alerts from anomaly detection
alerting rule (#236289)\n\nResolves
https://github.com/elastic/kibana/issues/235504\nCurrently, when an
ML-only user creates ML rules from both creation\nflows, the consumer is
set to `alerts`.\nCreating a rule from the \"Anomaly Detection Jobs\"
page in Stack\nmanagement sets the consumer to `stackAlerts` for a user
with access to\nboth feature privileges, instead of setting the consumer
to `alerts`.\nWith this PR, ML-only user will be able to access all ML
rules, no\nmatter if the consumer is `alerts` or `stackAlerts`.\n\n<img
width=\"896\" height=\"611\" alt=\"Screenshot 2025-09-25 at 13 42
19\"\nsrc=\"https://github.com/user-attachments/assets/14ec0af4-03fb-41e2-b3cf-de36106ed68c\"\n/>","sha":"7d682e38784717604aac8714ff9b7fd94dc3cac6"}},{"branch":"8.18","label":"v8.18.8","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/236577","number":236577,"state":"OPEN"},{"branch":"9.0","label":"v9.0.8","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.1","label":"v9.1.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/236578","number":236578,"state":"OPEN"}]}]
BACKPORT-->
niros1 pushed a commit that referenced this pull request Sep 30, 2025
@rbrtj @niros1
[ML] Anomaly Explorer: Fixes display of alerts from anomaly detection…
6aa40b5 
… alerting rule (#236289)

Resolves #235504
Currently, when an ML-only user creates ML rules from both creation
flows, the consumer is set to `alerts`.
Creating a rule from the "Anomaly Detection Jobs" page in Stack
management sets the consumer to `stackAlerts` for a user with access to
both feature privileges, instead of setting the consumer to `alerts`.
With this PR, ML-only user will be able to access all ML rules, no
matter if the consumer is `alerts` or `stackAlerts`.

<img width="896" height="611" alt="Screenshot 2025-09-25 at 13 42 19"
src="https://github.com/user-attachments/assets/14ec0af4-03fb-41e2-b3cf-de36106ed68c"
/>
rylnd pushed a commit to rylnd/kibana that referenced this pull request Oct 17, 2025
@rbrtj
[ML] Anomaly Explorer: Fixes display of alerts from anomaly detection…
c7e0c3c 
… alerting rule (elastic#236289)

Resolves elastic#235504
Currently, when an ML-only user creates ML rules from both creation
flows, the consumer is set to `alerts`.
Creating a rule from the "Anomaly Detection Jobs" page in Stack
management sets the consumer to `stackAlerts` for a user with access to
both feature privileges, instead of setting the consumer to `alerts`.
With this PR, ML-only user will be able to access all ML rules, no
matter if the consumer is `alerts` or `stackAlerts`.

<img width="896" height="611" alt="Screenshot 2025-09-25 at 13 42 19"
src="https://github.com/user-attachments/assets/14ec0af4-03fb-41e2-b3cf-de36106ed68c"
/>
@rbrtj rbrtj mentioned this pull request Nov 18, 2025
Closed
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 :ml release_note:fix Team:ML Team label for ML (also use :ml) t// v8.18.8 v8.19.5 v9.0.8 v9.1.5 v9.2.0

5 participants

@rbrtj @elasticmachine @kibanamachine @peteharverson @cnasikas