-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[RAM] Makes anomaly detection rule visible in Observability #170451
Conversation
Pinging @elastic/response-ops (Team:ResponseOps) |
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.
triggers actions UI changes LGTM
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management) |
FYI the PR to set anomaly description as an alert message |
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.
I reckon we should rename the const for consistency. The rest LGTM!
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.
D&R changes LGTM
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.
-
The name of the new rule is
Anomaly detection alert
which does not match the rest of the rules, can we remove thealert
keyword from this rule name? (Or was this name suggested by the PMs?) -
In case of not having an ML job, there is no option to create one from the flyout:
Is there a feature to add this option? (I assume not related to this PR just noticed it here)
-
Also, in case of having basic license, SLO rule is shown in disabled mode but the ML Anomaly one is not shown at all, is this expected?
The license error and the link to fix it is amaing 😍
return [ES_QUERY_ID, ...observabilityRuleTypeRegistry.list()]; | ||
return [ | ||
ES_QUERY_ID, | ||
ML_ANOMALY_DETECTION_RULE_TYPE_ID, |
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.
@vinaychandrasekhar @katrin-freihofner Currently, the Anomaly rule is the second item in the rules list, since it is Beta, should we move it to the end of the list? (Also, in case of no ML job, the flyout does not have an option to send the user to create one.)
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.
FYI It's not in Beta anymore :)
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.
I discussed this with Vinay, and the current order is good.
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
thanks for the feedback @maryam-saeidi!
I recall we called it like this to avoid confusion with the Anomaly detection as a feature itself. I don't have any objections to renaming it for consistency with the other rule types. @peteharverson wdyt?
Good point, created an issue for that #173654 , aiming to deliver in 8.13.
If you browse the Anomaly detection rule in the Rules management UI, it is disabled in a similar fashion as the SLO rule you mentioned. @XavierM can you please check if any additional config is needed here? |
Agree that for consistency we can remove |
@darnautov and @peteharverson |
@darnautov I just checked it and I do not see the same thing that you are seeing? I think the problem is here -> https://github.com/elastic/kibana/blob/main/x-pack/plugins/ml/public/plugin.ts#L207 because if you do not have a full license, you are not registering the anomaly detection rule. So that's why it is not showing up! |
FYI It's been renamed in #173545, cc @maryam-saeidi @XavierM |
@XavierM tested and realised we added some unnecessary guards for registering ML alerting rules. I created a PR to address it #173644. When it's merged the Anomaly detection rule type should be visible with the basic license as well, but the entry in the list is disabled. |
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
💚 Build Succeeded
Metrics [docs]Public APIs missing comments
Async chunks
Page load bundle
Unknown metric groupsAPI count
History
To update your PR or re-run it, just comment with: |
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!
Summary
From the rule management page in observability, user will be able to create an anomaly detection rule.