Warning, /swf-monitor/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 # Monitor base URL for REST endpoints used by alarm checks.
0010 service_base_url = "https://pandaserver02.sdcc.bnl.gov/swf-monitor"
0011 request_timeout = 20
0012 log_path = "/opt/swf-monitor/shared/logs/swf-alarms/run.log"
0013
0014 # Postgres - alarm state goes in swf-monitor's own DB. By default the
0015 # engine reads DB_* from swf-monitor's production.env so there is one
0016 # source of truth.
0017 [db]
0018 # env_path = "/opt/swf-monitor/config/env/production.env"
0019 # Or explicit DSN override:
0020 # dsn = "postgresql://admin:PASSWORD@localhost:5432/swfdb"
0021
0022 [email]
0023 provider = "ses"
0024 region = "us-east-1"
0025 from = "wenaus@gmail.com"
