Infrastructure Scenario Tests

We test Corax against real-world infrastructure failures across every vendor, platform, and scenario. Browse the results below.

21,502
Total Tests
100.0%
Pass Rate
21,502
Passed
0
Failed

Prometheus 2.51 Failed Graceful Shutdown — Killed with SIGKILL on SUSE Enterprise 15 SP5

PASS

Prometheus 2.51 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

InfrastructurePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Prometheus 2.51 Failed Graceful Shutdown — Killed with SIGKILL on AlmaLinux 9

PASS

Prometheus 2.51 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

InfrastructurePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Grafana 10.4 Failed Graceful Shutdown — Killed with SIGKILL on Amazon Linux 2023

PASS

Grafana 10.4 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

InfrastructurePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Grafana 10.4 Failed Graceful Shutdown — Killed with SIGKILL on SUSE Enterprise 15 SP5

PASS

Grafana 10.4 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

InfrastructurePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Elasticsearch 8.13 Failed Graceful Shutdown — Killed with SIGKILL on RHEL 9

PASS

Elasticsearch 8.13 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

InfrastructurePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Prometheus 2.51 Failed Graceful Shutdown — Killed with SIGKILL on Oracle Linux 9

PASS

Prometheus 2.51 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

InfrastructurePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Grafana 10.4 Failed Graceful Shutdown — Killed with SIGKILL on Ubuntu 24.04 LTS

PASS

Grafana 10.4 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

InfrastructurePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Prometheus 2.51 Failed Graceful Shutdown — Killed with SIGKILL on Fedora 40 Server

PASS

Prometheus 2.51 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

InfrastructurePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Prometheus 2.51 Failed Graceful Shutdown — Killed with SIGKILL on Ubuntu 24.04 LTS

PASS

Prometheus 2.51 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

InfrastructurePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Prometheus 2.51 Failed Graceful Shutdown — Killed with SIGKILL on CentOS 9 Stream

PASS

Prometheus 2.51 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

InfrastructurePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Prometheus 2.51 Failed Graceful Shutdown — Killed with SIGKILL on Ubuntu 22.04 LTS

PASS

Prometheus 2.51 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

InfrastructurePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Prometheus 2.51 Failed Graceful Shutdown — Killed with SIGKILL on Rocky Linux 9

PASS

Prometheus 2.51 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

InfrastructurePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Jaeger 1.55 High Disk IO Wait — Performance Degraded on Debian 12 Bookworm

PASS

Jaeger 1.55 performance is severely degraded due to disk I/O contention from another process on the same host.

InfrastructurePattern: STORAGE_IO_LATENCYSeverity: HIGHConfidence: 64%Auto-Heal

Jaeger 1.55 High Disk IO Wait — Performance Degraded on RHEL 9

PASS

Jaeger 1.55 performance is severely degraded due to disk I/O contention from another process on the same host.

InfrastructurePattern: STORAGE_IO_LATENCYSeverity: HIGHConfidence: 64%Auto-Heal

Jaeger 1.55 High Disk IO Wait — Performance Degraded on Rocky Linux 9

PASS

Jaeger 1.55 performance is severely degraded due to disk I/O contention from another process on the same host.

InfrastructurePattern: STORAGE_IO_LATENCYSeverity: HIGHConfidence: 64%Auto-Heal

Nagios Core 4.5 High Disk IO Wait — Performance Degraded on Arch Linux

PASS

Nagios Core 4.5 performance is severely degraded due to disk I/O contention from another process on the same host.

InfrastructurePattern: STORAGE_IO_LATENCYSeverity: HIGHConfidence: 64%Auto-Heal

Nagios Core 4.5 High Disk IO Wait — Performance Degraded on AlmaLinux 9

PASS

Nagios Core 4.5 performance is severely degraded due to disk I/O contention from another process on the same host.

InfrastructurePattern: STORAGE_IO_LATENCYSeverity: HIGHConfidence: 64%Auto-Heal

Nagios Core 4.5 High Disk IO Wait — Performance Degraded on SUSE Enterprise 15 SP5

PASS

Nagios Core 4.5 performance is severely degraded due to disk I/O contention from another process on the same host.

InfrastructurePattern: STORAGE_IO_LATENCYSeverity: HIGHConfidence: 64%Auto-Heal

Nagios Core 4.5 High Disk IO Wait — Performance Degraded on Oracle Linux 9

PASS

Nagios Core 4.5 performance is severely degraded due to disk I/O contention from another process on the same host.

InfrastructurePattern: STORAGE_IO_LATENCYSeverity: HIGHConfidence: 64%Auto-Heal

Nagios Core 4.5 High Disk IO Wait — Performance Degraded on Fedora 40 Server

PASS

Nagios Core 4.5 performance is severely degraded due to disk I/O contention from another process on the same host.

InfrastructurePattern: STORAGE_IO_LATENCYSeverity: HIGHConfidence: 64%Auto-Heal
PreviousPage 6 of 122Next

Every scenario is tested against Corax's Neural Engine in a production environment with AI-powered root cause analysis.

Tests run continuously as new infrastructure patterns are added.