Logging#

IncidentRelay writes structured JSON-style logs for alert intake, notifications, scheduler activity and errors.

Where to look#

Systemd installations:

Copyjournalctl -u incidentrelay -f
journalctl -u incidentrelay-scheduler -f

RPM installations use the same service names:

Copyjournalctl -u incidentrelay -f
journalctl -u incidentrelay-scheduler -f
journalctl -u incidentrelay-telegram-worker -f

Docker installations:

Copydocker compose logs -f incidentrelay
docker compose logs -f incidentrelay-scheduler

If file logging is configured:

Copytail -f /var/log/incidentrelay/incidentrelay.log

Useful fields#

Common fields:

Copytimestamp
level
logger
message
module
function
line

Alert and notification fields:

Copyalert_id
team
route_id
routing_error
channel_id
channel_name
channel_type
event_type
provider
error

Notification logs#

notification sent means IncidentRelay handed the message to the downstream provider or SMTP relay without an exception. It does not guarantee final delivery.

If a user did not receive a message, check the downstream service logs as well.