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