BeePanel shows its own health and the PBX's on two pages under Management: Status for the server and the connections, and Endpoints for device registrations. Both need a user allowed to manage BeePanel. For deeper detail, BeePanel writes a log file on the server. Nothing from these pages or the log is sent anywhere.
The Status page
Open Management > Status. The page refreshes every 15 seconds. When something needs attention, the Status tab carries a dot.
System
- CPU, Memory, and Recording disk usage, each with the last five minutes. Recording disk also shows the recording directory. When the disk fills up, see Storage and retention.
- A card with the BeePanel version, the Update entitlement end date, the Service uptime, the Asterisk version, the AMI version, the Operating system, the Server uptime, and the size of the Database. How to update? shows the update command; see Updating BeePanel.
The usage history is kept only in memory and starts again when the service restarts.
Services
| Row | States |
|---|---|
| Asterisk | Running, or No data while the AMI connection is down |
| AMI | Connected, Stale (open, but no events for a while), Disconnected, Not configured |
| Call history (CEL) | Active, Validating, Action required, Degraded, Not configured |
| Queue log | Running, Waiting, Needs attention, Not configured |
The AMI row also shows since when it is connected and how many times it has disconnected. The call history and queue log rows show their last event or line and the processing lag. When a row has a problem, it says what to check and where; the call history row also shows a diagnostic code. Each row is checked on its own, so one failing connection does not stop the others. Under the Standard edition, call history and the queue log carry the Pro mark.
For each connection, see AMI connection, Call history source, and Queue log.
Live
Active calls, Channels open on Asterisk, and Connected live clients, the panel and wallboard sessions, each with the last five minutes.
The Endpoints page
Management > Endpoints shows device registrations and line reachability as the PBX reports them. BeePanel reads them every 15 seconds while the page is open and visible and stores nothing.
- Extensions lists each extension with its registered devices: status, Device (User-Agent), Address, Latency, and Registration ends. An extension without a device reads No registered device.
- Lines lists each trunk with its status, address, latency, and Outbound registration.
- A device status is Reachable, High latency (150 ms or more), Unreachable, or Not measured when Asterisk does not measure it.
- Only problems shows only unreachable and high-latency rows. The search matches number, name, User-Agent, and address.
- Device software counts devices by the exact User-Agent text they send.
Without a PBX connection the page shows that the live inventory is unavailable.
Logs
BeePanel writes its log to /var/log/beepanel/beepanel.log as JSON lines.
The file rotates at 10 MiB and five older files are kept, from
beepanel.log.1 to beepanel.log.5. The log holds no passwords, secrets, or
license keys.
The log level is info by default. For more detail, set it to debug in
/opt/beepanel/config/beepanel.json as root:
"logging": { "level": "debug" }The accepted levels are debug, info, warn, and error. Restart the
service to apply it, and set it back to info when you are done:
systemctl restart beepanelAn invalid level stops the service from starting. When the service does not start at all, its reason is in the system journal:
journalctl -u beepanel