Operations

Service status

sudo systemctl status stellar-alert-case-syslog

Follow logs

sudo journalctl -u stellar-alert-case-syslog -f

Recent logs only:

sudo journalctl -u stellar-alert-case-syslog -n 100 --no-pager

Restart

sudo systemctl restart stellar-alert-case-syslog

Reconfigure

Run the wizard again:

python3 Stellar_Alert_Case_Syslog.py --setup

Review the summary before applying the new service configuration.

Installed files

The wizard uses:

/usr/local/lib/stellar-alert-case/Stellar_Alert_Case_Syslog.py
/etc/default/stellar-alert-case-syslog
/etc/systemd/system/stellar-alert-case-syslog.service

The token environment file is root-only. The service uses automatic restart and a restrictive umask.

Runtime state

By default:

~/.local/state/stellar_alert_case/
├── queue.db
├── logs/
└── stellar_alert_case.lock

Do not run multiple instances against the same state directory.

Backfill

--backfill DAYS intentionally re-fetches historical data and can resend records. Use it only for controlled testing or recovery.

Overview

Get started

Operations

Operations

Operations

Service status

Follow logs

Restart

Reconfigure

Installed files

Runtime state

Backfill

​Operations

​Service status

​Follow logs

​Restart

​Reconfigure

​Installed files

​Runtime state

​Backfill

Operations

Service status

Follow logs

Restart

Reconfigure

Installed files

Runtime state

Backfill