Files
felhom.eu/hub/configs/hub.yaml.example
T
admin e531516cfa Hub: add POST /api/v1/notify endpoint for customer notifications
- New notification relay endpoint: receives events from customer controllers,
  looks up customer email preferences, sends via Resend HTTP API
- New tables: customer_notifications (per-customer email + event prefs),
  notification_log (audit trail for all notification attempts)
- Hungarian email template with severity, event type, timestamp
- Config: notifications.resend_api_key + notifications.from_email
- Test events always pass event-type filter

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-16 19:29:55 +01:00

38 lines
1.2 KiB
Plaintext

# =============================================================================
# Felhom Hub Configuration
# =============================================================================
# Location: /etc/felhom-hub/hub.yaml (or mount as ConfigMap in k8s)
#
# The hub receives health reports from customer controllers and serves
# a multi-customer overview dashboard for the operator.
# =============================================================================
# --- Authentication ---
auth:
# Bcrypt hash for dashboard login (Viktor only)
password_hash: ""
# --- API ---
api:
# Bearer token required for report ingest (POST /api/v1/report)
report_api_key: ""
# --- Notifications ---
notifications:
resend_api_key: "" # Resend.com API key for sending notification emails
from_email: "monitoring@felhom.eu" # Sender address for notification emails
# --- Data retention ---
retention:
max_days: 90 # Keep 90 days of report history
prune_schedule: "04:30" # Daily prune time (Europe/Budapest)
# --- Alerting thresholds ---
alerting:
stale_threshold: "30m" # Customer considered stale if no report for this duration
# --- Server ---
server:
listen: ":8080"
data_dir: "/data" # SQLite database location