Diagnostics

Health check endpoints

The following local endpoints confirm that each application component is running:

Endpoint

Component

http://127.0.0.1:9200/

Elasticsearch

http://127.0.0.1:9000/base

Energy SOAR Base

http://127.0.0.1:9001/automation

Energy SOAR Automation (Cortex)

Quick check:

curl -I http://127.0.0.1:9200/
curl -I http://127.0.0.1:9000/base
curl -I http://127.0.0.1:9001/automation

An HTTP 200 response from each endpoint confirms the service is accepting requests.

Status collection script

The status script collects a diagnostic snapshot of the entire system and packages it into a single archive for support:

/opt/energysoar/lib/extra/energysoar_status.sh

The script collects:

  • CPU and memory usage (top, free)

  • Disk usage (df)

  • Systemd journal logs for: energysoar, cortex, n8n, nginx, elasticsearch

  • HTTP response headers from the three health check endpoints

  • Java version

Output is written to /tmp/soar_logs.tar.gz. Send this file to support when reporting an issue.

Log files

Application logs are written to the following locations:

File

Content

/var/log/energysoar/application.log

Energy SOAR Base events

/var/log/energysoar/n8n.log

Workflow engine events

/var/log/cortex/application.log

Automation (Cortex) events

/var/log/nginx/access.log

nginx access log

/var/log/nginx/error.log

nginx error log

/var/log/elasticsearch/elasticsearch.log

Elasticsearch events

Log policy (rotation, levels, output targets) is configured in /etc/energysoar/logback.xml.