CMS Alert Manager Settings
These settings mainly involves CMS communication with other nodes using MQTT and connections to the alert database.
| Format | Path | Filename | Purpose |
|---|---|---|---|
| JSON | ./conf/mops-cms-alertmgr/ |
config.json |
MQTT configuration |
| JSON | ./conf/mops-cms-alertmgr/ |
db-config.json |
Database configuration |
Configuration file example config.json:
{
"mqtt": {
"protocol": "tcp",
"host": "mops-event-broker",
"port": 1883,
"mqttVersion": 4,
"reconnect": 1000,
"timeout": 30000,
"path": "/event",
"rootPath": "mops/historian/SITE/#"
}
}
Description of config.json keys and values:
| Name | Type | Description |
|---|---|---|
| protocol | string | “tcp” as default. “ws”, “wss” for websockets/secure websockets. |
| host | string | Host name of broker container. Typically “mops-event-broker” or “ingress”. |
| port | int | Port used on host for MQTT. Typically 1883, if host=ingress it is 80 to route through for MQTT-connection or 9001 for a websockets connection. |
| mqttVersion | int | Version of MQTT protocol. Typically 4 or 5. |
| reconnect | int | The time in milliseconds before attempting to reconnect after a disconnection |
| timeout | int | The time in milliseconds to wait for a connection to be established before timing out |
| path | string | MQTT over Websockets can configure a path. Typically “/event”. |
| rootPath | string | MQTT Topic filter. Wildcards as /+/ matches all topics in a certain level. |
Configuration file example of db-config.json:
{
"database": "alertdb",
"user": "u_alertdb",
"password": "<password>",
"host": "mpoks-db02.tl.pvt",
"port": "5432"
}
Description of db-config.json keys and values:
| Name | Type | Description |
|---|---|---|
| database | string | Database name. Typically “alertdb”. |
| user | string | Database user name. Typically “u_alertdb”. |
| password | string | Database password. |
| host | string | Database server address. |
| port | string | Database port number. Typically “5432”. |