Control Host Statistics

MaaS monitors the health and performance of your TMedia host servers and individual application processes. For 1+1 redundant deployments, each host is discovered and monitored separately with role identification.

---

Host Discovery

Hosts are automatically discovered from your TMedia configuration. The following information is captured:

Attribute	Description
Host Name	Configured hostname
Role	Primary or Secondary (for 1+1 systems)
Serial Number	Hardware serial number
Firewall Status	Whether TBRouter firewall is enabled

---

Host Status Metrics

Statistic	Type	Description
Host State	Text	Operational state (Up/Down)
Reboot Required	Text	Whether a reboot is pending
Scheduling Problem	Count	Number of scheduling issues detected
License Expired	Text	License expiration status
License Expiring Soon	Text	License approaching expiration

---

Host Performance Metrics

Statistic	Units	Description
CPU Usage	%	Overall CPU utilization
RAM Usage	%	Memory utilization
File System Used	%	Disk space utilization
File System Free	%	Available disk space (calculated)

---

Host Information

Statistic	Description
Firmware Version	Current software version
Serial Number	Hardware identification

---

Host Alerts

High Severity

Alert	Condition	Description
Host Down	State ≠ "Up"	Host is not operational
File System 95%	Disk > 95%	Critical disk space

Warning Severity

Alert	Condition	Description
File System 80%	Disk > 80%	Elevated disk usage

---

Application Statistics

MaaS discovers and monitors individual application processes running on each host.

Application Metrics

Statistic	Type	Description
App State	Text	Application operational state
HA State	Text	High availability state
App CPU	%	Per-application CPU usage

Common Applications Monitored

Application	Internal Name	Description
Toolpack System Manager	toolpack_sys_mgr	Core system management
TBOAM App	tboam_app	OAM application
SNMP Agent	tbsnmpagent	SNMP interface
Stream Server	stream_server	Media streaming
TB Router	tbrouter	Firewall/routing (if enabled)
MySQL	mysqld	Database server
Ruby	ruby	Web interface
SNMP Daemon	snmpd	SNMP service
Sig Trace	tbsigtrace	Signaling trace
CLI Tools	tbx_cli_tools_remote	Remote CLI
IP Watchdog	ipwatchd	IP monitoring
KNI Single	kni_single	Kernel network interface

---

Application Alerts

High Severity

Alert	Condition	Description
App CPU 95%	5-min avg > 94%	Critical CPU usage

Warning Severity

Alert	Condition	Description
App CPU 80%	15-min avg > 79%	Elevated CPU usage

---

Understanding HA States

For 1+1 redundant deployments, application HA states indicate:

State	Meaning
Active	Application is handling traffic
Standby	Application is ready for failover
Not Ready	Application is not in a ready state

---

Performance Troubleshooting

1

High Host CPU — Step 1

Check per-application CPU to identify the culprit.

2

High Host CPU — Step 2

Investigate common causes:

• High call volume

• Media transcoding

• Logging overhead

3

High Host CPU — Step 3

Take corrective actions based on the identified application or cause (e.g., tune application, offload transcoding, adjust logging).

High RAM Usage

Memory issues may indicate:

• Memory leaks (check application states)

• Insufficient resources for call volume

• Logging or caching issues

Disk Space Issues

Common causes of disk space consumption:

• CDR/log accumulation

• Core dumps

• Signaling traces

---

Monitoring Best Practices

Baseline Your Environment

During normal operation, note typical values for:

• Host CPU and RAM utilization

• Per-application CPU usage

• Disk space consumption rate

Set Appropriate Thresholds

Default thresholds (80%/95%) work for most deployments, but you may need to adjust based on your baseline if your system normally runs at higher utilization.

Monitor Both Hosts

In 1+1 deployments, don't ignore the standby host. Issues on standby will become problems during failover.