Onboard APM Anomaly rule type with FAAD #179196
Conversation
|
/ci |
doakalexi
changed the title
doakalexi
added
Team:ResponseOps
|
Pinging @elastic/response-ops (Team:ResponseOps) |
| }); | ||
| if (!alerting) { | ||
| throw new Error( | ||
| 'Cannot register anomaly rule type. Both the actions and alerting plugins need to be enabled.' |
There was a problem hiding this comment.
Is the actions plugin actually required? Can't tell from this PR anyway (or I didn't notice).
There was a problem hiding this comment.
You are right I don't think it's actually required, thanks for catching! I will update the error message in this PR and the others.
There was a problem hiding this comment.
Resolved in this commit 193c433
botelastic
bot
added
the
Team:obs-ux-infra_services
|
Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services) |
…na into move-anomaly-rule-to-faad
peteharverson
changed the title
|
@doakalexi I made a minor edit to the PR title and description to clarify that this is for the APM Anomaly rule, rather than the anomaly detection rule under Machine Learning (which has already been onboarded with FAAD).
I believe the Observability team has an indexer tool that's now available from within Kibana, it was a separate repo before. This can create spikes in the data on the fly, but I'm not sure it can create historic data to train the anomaly detection job first which would be necessary for the job to generate anomalies and therefore create alerts. The Obs team might know more. |
Thank you! 🙂 |
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: cc @doakalexi |
towards: #169867
This PR onboards APM Anomaly rule type with FAAD.
I am having trouble getting this rule to create an alert. If there is any easy way to verify pls let me know!