Warning, /swf-remote/alarms/config.toml.example is written in an unsupported language. File is not indexed.
0001 # swf-alarms engine config — copy to config.toml.
0002 #
0003 # Alarm *configurations* (thresholds, recipients, severities, enabled flags)
0004 # live in the DB as kind='alarm' entries in the swf-alarms context. Edit
0005 # them in the dashboard UI, not here. This file only has settings the
0006 # engine itself needs to start up.
0007
0008 [engine]
0009 # Loopback through swf-remote's Apache. swf-remote owns the SSH tunnel
0010 # to pandaserver02; this engine never talks to BNL directly.
0011 swf_remote_base_url = "https://epic-devcloud.org/prod"
0012 request_timeout = 20
0013 log_path = "/var/log/swf-alarms/run.log"
0014
0015 # Postgres — alarm state goes in swf-remote's own DB. By default the
0016 # engine reads SWF_REMOTE_DB_* from swf-remote's .env so there is one
0017 # source of truth.
0018 [db]
0019 # env_path = "/var/www/swf-remote/src/.env"
0020 # Or explicit DSN override:
0021 # dsn = "postgresql://swf_remote:PASSWORD@localhost:5432/swf_remote"
0022
0023 [email]
0024 provider = "ses"
0025 region = "us-east-1"
0026 from = "wenaus@gmail.com"
