Help Center← Back to Dashboard
Getting Started
What is Aithroyz?Quickstart: First EnvironmentCloud CredentialsPlans & Approvals
Environments
OverviewLifecycle PhasesTTL Auto-DestroyExtending TTLDestroying an Environment
Tools Reference
OverviewElastic Stack (SIEM)Wazuh (XDR)MITRE CalderaTheHive & DFIR-IRISVelociraptorOpenCTIGrafana + PrometheusShuffle SOARn8nUptime KumaLLM GatewayOpen WebUIFlowiseOpenClawOllamaQdrantLangfusePortainerGiteaSonarQubeCode ServerMattermostMinIOMetabaseHashiCorp VaultKeycloak SSONetBoxLocalStack
Access & Security
Google SSOTenant IsolationPasskeys & MFATeam Members
API & Integrations
API KeysMCP Tools (Clevername)Terraform ExportWebhooks & Callbacks
Stack Presets
SOC PlatformIR / DFIR LabThreat HuntingQuick Sandbox
Settings
Cloud KeysAPI KeysBillingAudit Log
Troubleshooting
Common IssuesDeployment FailuresDNS & ConnectivityTool Health Checks
Aithroyz Help
Help CenterTroubleshootingTool Health Checks

Tool Health Checks

After deployment, Aithroyz runs health checks on each tool. A failing health check means the tool isn't ready yet — here's how to interpret and resolve them.

Health badge meanings

Green
Tool is responding to health check requests with 200 or 302 (login redirect). Fully operational.
Amber
Tool is starting up or initializing. Health check is returning a non-OK status. Wait and refresh — some tools take 10–15 minutes.
Red
Tool is unreachable — either the container crashed, the VM is down, or the health check timed out.
Gray
Health check has not been run yet, or is not configured for this tool.

Expected startup times

ToolTimeNotes
Elastic Stack
2–4 min
Fast — Elasticsearch starts quickly once JVM heap is allocated
Wazuh
3–6 min
Indexer, manager, and dashboard must all initialize
MITRE Caldera
8–15 min
Stockpile and Atomic plugins load the full ATT&CK knowledge base — takes time
TheHive
3–5 min
JVM-based, needs 4 GB RAM minimum
DFIR-IRIS
2–3 min
Python/Gunicorn — relatively fast
Velociraptor
1–2 min
Binary service, very fast startup
OpenCTI
8–12 min
Elasticsearch + RabbitMQ + MinIO all must start before OpenCTI is healthy
Grafana + Prometheus
1–2 min
Both start quickly
Shuffle SOAR
2–3 min
Docker-based, moderate startup
n8n
1–2 min
Node.js, fast startup
✓
To diagnose a red health badge, open Portainer (https://portainer.{env-name}.ops.aithroyz.com) and check the container logs for the failing tool. Portainer is always deployed as part of the foundation and is not affected by tool failures.
Related Articles
Deployment FailuresRead article →Environments OverviewRead article →