centralcloud/oncall-engine
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update escalation auditor logs to expose succeeding count (#4431)

Browse source 
Related to https://github.com/grafana/oncall-private/issues/2619
(we need the succeeding number to make the SLO query happy with
cluster/namespace filtering)
This commit is contained in:
Matias Bordese 2024-05-31 15:29:31 -03:00 • committed by GitHub
parent d8e1a1dfae
commit 2aa8639e2a
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 3 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
engine/apps/alerts/tasks/check_escalation_finished.py
View file

@ -229,8 +229,9 @@ def check_escalation_finished_task() -> None:
if total_alert_groups_count == 0
else (total_alert_groups_count - failed_alert_groups_count) / total_alert_groups_count * 100
)
task_logger.info(f"Alert groups that failed escalation: {failed_alert_groups_count}")
task_logger.info(f"Alert groups total: {total_alert_groups_count}")
task_logger.info(f"Alert groups failing escalation: {failed_alert_groups_count}")
task_logger.info(f"Alert groups succeeding escalation: {total_alert_groups_count - failed_alert_groups_count}")
task_logger.info(f"Alert groups total escalations: {total_alert_groups_count}")
task_logger.info(f"Alert group notifications success ratio: {success_ratio:.2f}")
if alert_group_ids_that_failed_audit: