Fixes the critical alerts exception with the start_time > end_time

Signed-off-by: Tullio Sebastiani <tsebasti@redhat.com>
This commit is contained in:
Tullio Sebastiani
2024-01-15 11:11:45 -05:00
committed by Naga Ravi Chaitanya Elluri
parent 631f12bdff
commit aa030a21d3
+8 -1
View File
@@ -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)