Repository navigation
Expand file tree
/
Copy pathexample.conf
More file actions
49 lines (37 loc) · 2.22 KB
/
Copy pathexample.conf
File metadata and controls
49 lines (37 loc) · 2.22 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
#START of MTGuardianX config file
# MTGuardianX section
# This variable indicate if we *additionally* will log all messages to the (vistual) console, logging to syslog is ALWAYS ON
LOG_TO_CONSOLE=1
# This variable defines logger tag - will be added to the log line in syslog - you can use the same name as for profile name or whatever but no spaces!
LOGGER_TAG=mtguardianx-prod
# This variable defines server name which will be used in the notification messages. Here you can write ANYTHING what you want to be known for your server name
MT_CORE_SERVER_NAME='Production server'
# This variable indicates how long time (in seconds) MTGuardianX will wait before perform MTCore instanse restart with the same profile
MT_CORE_RESTART_DELAY=2
# Restart storm protection. Normal crashes use MT_CORE_RESTART_DELAY. Repeated immediate crashes back off up to MT_CORE_MAX_RESTART_DELAY.
MT_CORE_MAX_RESTARTS_PER_WINDOW=5
MT_CORE_RESTART_WINDOW_SECONDS=60
MT_CORE_MAX_RESTART_DELAY=60
# Operator state/reporting. These writes are best-effort and do not control restart reliability.
MTGX_STATE_ROOT=/run/mtguardianx
MTGX_LOG_ROOT=/var/log/mtguardianx
MTGX_REPORT_LOG_LINES=1000
MTGX_LOG_GLOBS=('/opt/mtcore/logs/*.log')
MTGX_ALLOW_REQUEST_RESTART=0
# TG notifications section
# This variable indicate if we need to send Telegram (TG) notifications. Change to 0 if you do not need TG notifications at all.
TG_NOTIFICATIONS=0
# Here you must add TG API token and your chat ID in case you want TG notifications. Check TG documentation for more details how to get API token and Chat ID
# This variable contain TG API token
TG_API_TOKEN=''
# This variable contain LIST of the channels where we need to send notifications
TG_CHAT_ID=''
# MTCore section
# This variable contain full path to MTCore. In case you are using different versions (builds) - you can define a custom path to the MTCore
MT_CORE_DIR=/home/mt-service/monitoring/simulation
# Recommended array form. It preserves arguments containing spaces.
MT_CORE_ARGS=(--no-update)
# This variable contains profile name for MTCore. It will be used to monitor ONLY this MTCore instance.
# Underscores are allowed for real fleet profiles such as Tour_IRN_003.
MT_CORE_PROFILE=Tour_IRN_003
#END of MTGuardianX config file