chore: improve log lines metadata

[alexluong]

addresses #605

Summary

Standardizes logging across the event delivery pipeline to make debugging easier. All delivery-related logs now consistently include:

• event_id - the published event
• tenant_id - for multi-tenant filtering
• destination_id - target destination
• destination_type - type of destination (webhook, sqs, etc.)

Log Fields

Log Message	Level	event_id	tenant_id	destination_id	destination_type	Notes
processing delivery event	INFO	✓	✓	✓	-
failed to publish event	ERROR	✓	✓	✓	✓
failed to cancel scheduled retry	ERROR	✓	✓	✓	✓	+ retry_id
scheduled retry canceled	AUDIT	✓	✓	✓	✓	+ retry_id
event delivered	AUDIT	✓	✓	✓	✓
failed to publish delivery log	ERROR	✓	✓	✓	✓
failed to handle alert attempt	ERROR	✓	✓	✓	✓
alert attempt handled	INFO	✓	✓	✓	✓
failed to schedule retry	ERROR	✓	✓	✓	-
retry scheduled	AUDIT	✓	✓	✓	-
destination deleted	INFO	✓	✓	✓	-
failed to retrieve destination	ERROR	✓	✓	✓	-
destination not found	INFO	✓	✓	✓	-
skipping disabled destination	INFO	✓	✓	✓	✓
processing event	AUDIT	✓	✓	✓	-
failed to match event destinations	ERROR	✓	✓	-	-
no matching destinations	INFO	✓	✓	-	-
failed to retrieve destination	WARN	✓	✓	✓	-
failed to enqueue delivery event	ERROR	✓	✓	✓	-
delivery event enqueued	AUDIT	✓	✓	✓	-
destination disabled	AUDIT	✓	✓	✓	✓
failed to send alert	ERROR	✓	✓	✓	✓
alert sent	AUDIT	✓	✓	✓	✓
manual retry initiated	AUDIT	✓	✓	✓	✓

Context-specific fields:

• attempt - for retry-related logs
• manual - for manual retry logs
• delivery_status - for completed deliveries
• backoff - for retry scheduling
• error - for error logs

Do NOT include:

• delivery_event_id - internal implementation detail, not an exposed entity

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
outpost-docs	Ready	Preview, Comment	Jan 5, 2026 9:37am
outpost-website	Ready	Preview, Comment	Jan 5, 2026 9:37am