-
Notifications
You must be signed in to change notification settings - Fork 8.5k
[Response Ops][Alerting] Grouping ad hoc run metrics under alerting metrics #233875
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
Conversation
@elasticmachine merge upstream |
@elasticmachine merge upstream |
Pinging @elastic/response-ops (Team:ResponseOps) |
|
||
export function getTaskTypeGroup(taskType: string): string | undefined { | ||
// we want to group ad hoc runs under alerting | ||
if (taskType === 'ad_hoc_run-backfill') { |
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.
Using BACKFILL_TASK_TYPE
const from the alerting plugin could be better.
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
Tested locally and observed the expected results.
"alerting":{"success":1,"not_timed_out":1,"total":1,"total_errors":0,"rescheduled_failures":0,"user_errors":0,"framework_errors":0},"ad_hoc_run-backfill":{"success":1,"not_timed_out":1,"total":1,"total_errors":0,"rescheduled_failures":0,"user_errors":0,"framework_errors":0}
Just left a nit.
@elasticmachine merge upstream |
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]
History
cc @ymao1 |
…etrics (elastic#233875) Towards elastic/response-ops-team#297 ## Summary Updates the grouping for task manager per task type metrics to categorize `ad_hoc_run-backfill` task types under the `alerting` grouping. ## To Verify 1. Start ES and Kibana 2. Create a detection rule 3. Manually schedule a backfill for the detection rule 4. Navigate to the task manager metrics endpoint(https://localhost:5601/api/task_manager/metrics?reset=false) and verify that the success counter for `alerting` (under `metrics.task_run.value.by_type.alerting`) is incremented, as well as the success counter for `ad_hoc_run-backfill` (under `metrics.task_run.value.by_type.ad_hoc_run-backfill`). (The counters reset every 30 seconds so you will have to look at this endpoint quickly after scheduling the backfill). Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
…etrics (#233875) Towards elastic/response-ops-team#297 ## Summary Updates the grouping for task manager per task type metrics to categorize `ad_hoc_run-backfill` task types under the `alerting` grouping. ## To Verify 1. Start ES and Kibana 2. Create a detection rule 3. Manually schedule a backfill for the detection rule 4. Navigate to the task manager metrics endpoint(https://localhost:5601/api/task_manager/metrics?reset=false) and verify that the success counter for `alerting` (under `metrics.task_run.value.by_type.alerting`) is incremented, as well as the success counter for `ad_hoc_run-backfill` (under `metrics.task_run.value.by_type.ad_hoc_run-backfill`). (The counters reset every 30 seconds so you will have to look at this endpoint quickly after scheduling the backfill). Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Towards https://github.com/elastic/response-ops-team/issues/297
Summary
Updates the grouping for task manager per task type metrics to categorize
ad_hoc_run-backfill
task types under thealerting
grouping.To Verify
alerting
(undermetrics.task_run.value.by_type.alerting
) is incremented, as well as the success counter forad_hoc_run-backfill
(undermetrics.task_run.value.by_type.ad_hoc_run-backfill
). (The counters reset every 30 seconds so you will have to look at this endpoint quickly after scheduling the backfill).