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

Apache Kafka 3.7 Container OOM Killed — Memory Limit Hit on Debian 12 Bookworm

PASS

Apache Kafka 3.7 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

queuePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

NATS 2.10 Container OOM Killed — Memory Limit Hit on Ubuntu 24.04 LTS

PASS

NATS 2.10 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

queuePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Apache Kafka 3.7 Container OOM Killed — Memory Limit Hit on Amazon Linux 2023

PASS

Apache Kafka 3.7 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

queuePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Apache Kafka 3.7 Container OOM Killed — Memory Limit Hit on Ubuntu 24.04 LTS

PASS

Apache Kafka 3.7 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

queuePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

NATS 2.10 Container OOM Killed — Memory Limit Hit on AlmaLinux 9

PASS

NATS 2.10 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

queuePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

RabbitMQ 3.13 Container OOM Killed — Memory Limit Hit on Oracle Linux 9

PASS

RabbitMQ 3.13 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

queuePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

RabbitMQ 3.13 Container OOM Killed — Memory Limit Hit on Fedora 40 Server

PASS

RabbitMQ 3.13 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

queuePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

NATS 2.10 Container OOM Killed — Memory Limit Hit on Fedora 40 Server

PASS

NATS 2.10 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

queuePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

RabbitMQ 3.13 Container OOM Killed — Memory Limit Hit on Amazon Linux 2023

PASS

RabbitMQ 3.13 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

queuePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

RabbitMQ 3.13 Container OOM Killed — Memory Limit Hit on SUSE Enterprise 15 SP5

PASS

RabbitMQ 3.13 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

queuePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

RabbitMQ 3.13 Container OOM Killed — Memory Limit Hit on Arch Linux

PASS

RabbitMQ 3.13 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

queuePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

RabbitMQ 3.13 Container OOM Killed — Memory Limit Hit on AlmaLinux 9

PASS

RabbitMQ 3.13 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

queuePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

NATS 2.10 Container OOM Killed — Memory Limit Hit on Arch Linux

PASS

NATS 2.10 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

queuePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

RabbitMQ 3.13 Container OOM Killed — Memory Limit Hit on CentOS 9 Stream

PASS

RabbitMQ 3.13 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

queuePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

RabbitMQ 3.13 Container OOM Killed — Memory Limit Hit on Rocky Linux 9

PASS

RabbitMQ 3.13 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

queuePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

RabbitMQ 3.13 Container OOM Killed — Memory Limit Hit on Ubuntu 24.04 LTS

PASS

RabbitMQ 3.13 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

queuePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

RabbitMQ 3.13 Container OOM Killed — Memory Limit Hit on Debian 12 Bookworm

PASS

RabbitMQ 3.13 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

queuePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Apache Kafka 3.7 Container OOM Killed — Memory Limit Hit on Ubuntu 22.04 LTS

PASS

Apache Kafka 3.7 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

queuePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

RabbitMQ 3.13 Container OOM Killed — Memory Limit Hit on RHEL 9

PASS

RabbitMQ 3.13 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

queuePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

RabbitMQ 3.13 Container OOM Killed — Memory Limit Hit on Ubuntu 22.04 LTS

PASS

RabbitMQ 3.13 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

queuePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal
PreviousPage 20 of 116Next

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.