General
Monitoring
Trunks
Dynamically discovered from the latest status. These selections are saved now, but will only affect dashboards, alerts, metrics and SLA in the next phase.
SIP Trunk Discovery
Defines how each applicable server discovers its trunks. Servers without SIP monitoring should use the driver none.
vm-freepbx-eastus2-002 PJSIP Default prefixes: TRK-, EXT_TRK- 16 trunks found
vm-vicidial011-pr-eastus2-001 SIP All chan_sip peers 2 trunks found
vm-vicidial011-pr-eastus2-002 SIP All chan_sip peers 2 trunks found
vm-vicidial011-pr-eastus2-003 SIP All chan_sip peers 2 trunks found
vm-vicidial011-pr-eastus2-004 SIP All chan_sip peers 2 trunks found
vm-vicidial011-pr-eastus2-005 SIP All chan_sip peers 2 trunks found
vm-asterisk-eastus2-001 PJSIP Custom prefixes: astretell, devicidial, freepbx, prvicidial, qavicidial, sbc 10 trunks found
vm-astretell-eastus2-001 PJSIP Custom prefixes: asterisk, retell 2 trunks found
Enable trunk discovery on another server Select only a server that runs Asterisk
Servers
vm-freepbx-eastus2-002 192.168.241.4
vm-vicidtb011-pr-eastus2-001 192.168.251.21
vm-viciweb011-pr-eastus2-001 192.168.251.31
vm-vicidial011-pr-eastus2-001 192.168.251.41
vm-vicidial011-pr-eastus2-002 192.168.251.42
vm-vicidial011-pr-eastus2-003 192.168.251.43
vm-vicidial011-pr-eastus2-004 192.168.251.44
vm-vicidial011-pr-eastus2-005 192.168.251.45
vm-asterisk-eastus2-001 192.168.241.23
vm-astretell-eastus2-001 192.168.241.25
Add ServerCreate a new monitored server
URLs
Configure the HTTP or HTTPS endpoints checked by Watcher.
k360 https://solucion.kontactum360.com/
viciapi-v11 https://app-k360-apivici11-pr.azurewebsites.net/
vicidial-v11 https://pr-v11-viciweb.kontactum360.com/agc/vicidial.php
Add URLCreate a new HTTP/HTTPS check
Databases
Configure database connectivity and alert thresholds. Credentials remain in their external file and are never displayed here.
vicidial-pr MYSQL · 192.168.251.21:3306 · Enabled
azure-sql-principal AZURE_SQL · sql-kontactum360.database.windows.net:1433 · Enabled
azure-sql-crm-pr AZURE_SQL · sql-kontactum360.database.windows.net:1433 · Enabled
Add DatabaseCreate a new database check
SLA Targets
Notifications
Each channel toggle updates both the notification manager and the channel itself. Existing secrets are preserved when replacement fields are left blank.
Setup Requirements
Saving a record does not install software, create remote users or open network access. Complete the applicable requirements before enabling a monitor.
Servers and Services
- Watcher must reach the server over ICMP and/or SSH.
- The configured SSH user and key must authenticate non-interactively.
- Commands that require elevation must be allowed through narrowly scoped
sudo -nrules. - System services require their real service name; custom checks require a safe, non-interactive command.
SIP, PJSIP and IAX2 Trunks
- Asterisk must be installed at
/usr/sbin/asteriskon the remote server. - The SSH user must be allowed to run the selected Asterisk command with
sudo -n. - SIP runs
sip show peersand includes every non-numeric peer. - PJSIP runs
pjsip show registrationsandpjsip show aors; blank custom prefixes useTRK-andEXT_TRK-. - IAX2 runs
iax2 show peersand includes every non-numeric peer. - Choose NONE for servers that do not run Asterisk.
URLs and SSL
- Only complete HTTP or HTTPS addresses are accepted.
- Watcher requires DNS resolution and outbound network access to the destination.
- HTTPS checks require a reachable TLS endpoint with a certificate chain the operating system can validate.
- Saving a URL does not change DNS, certificates, proxies or firewalls.
MySQL, MariaDB and Azure SQL
- Supported engines are MySQL, MariaDB and Azure SQL. PostgreSQL is not implemented.
- The local client must exist at
/usr/bin/mysql. - The credentials file must use MySQL
--defaults-extra-fileformat and contain the effective host, port, user and password. - Azure SQL uses an external protected JSON credentials file containing
usernameandpassword. - Azure SQL requires TCP 1433, TLS connectivity and
VIEW DATABASE STATEfor complete diagnostic metrics. - The Watcher process must be able to read the credentials file; do not expose its contents in the web application.
- The database user needs access to global status/variables and the required
information_schemadiagnostic tables. - Replication monitoring is not implemented yet, even though the configuration flag exists.
Notifications
- Telegram requires a valid bot token and chat ID.
- Microsoft Teams requires a valid incoming webhook URL.
- Email requires the configured account to exist in the host mail integration and recipients to be valid.
- Secrets should be replaced only when intentionally rotating them; existing values are never displayed.