From aa030a21d3d6ec08f75f6e6d5be138f34254b8d4 Mon Sep 17 00:00:00 2001 From: Tullio Sebastiani Date: Mon, 15 Jan 2024 11:51:11 +0100 Subject: [PATCH] Fixes the critical alerts exception with the start_time > end_time Signed-off-by: Tullio Sebastiani --- run_kraken.py | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/run_kraken.py b/run_kraken.py index 990027be..267b5322 100644 --- a/run_kraken.py +++ b/run_kraken.py @@ -203,6 +203,7 @@ def main(cfg): # Capture the start time start_time = int(time.time()) + chaos_telemetry = ChaosRunTelemetry() chaos_telemetry.run_uuid = run_uuid # Loop to run the chaos starts here @@ -345,7 +346,13 @@ def main(cfg): ##PROM query = r"""ALERTS{severity="critical"}""" - critical_alerts = prometheus.process_prom_query_in_range(query, datetime.datetime.fromtimestamp(start_time)) + end_time = datetime.datetime.now() + critical_alerts = prometheus.process_prom_query_in_range( + query, + start_time = datetime.datetime.fromtimestamp(start_time), + end_time = end_time + + ) critical_alerts_count = len(critical_alerts) if critical_alerts_count > 0: logging.error("Critical alerts are firing: %s", critical_alerts)