Skip to content
Thirdlane

Services Status

Services Status gives you a single, real-time health check for everything the platform runs on - the PBX, SIP routing, database, web server, and supporting containers - without logging into the server. It is the fastest way to answer “is a service down?” when something is not working, and to spot a stopped or resource-hungry component before it causes a wider outage. The view is organized into three tabs: Systemd Services, Docker Containers, and Monitoring (Monit). Access it from Reports > Services Status in Configuration Manager.

Each tab has a Refresh button to reload the data on demand. Click the pencil icon on any row to open a detail form with additional information about that service.

Systemd Services

Displays systemd-managed services on the server, including PBX, Kamailio, Nginx, MariaDB, and other platform components.

Grid columns:

  • Name - the systemd unit name
  • Status - badge indicator (running or stopped)
  • Description - brief description of the service
  • Memory - current memory usage (cgroup total, includes child processes)
  • PID - main process ID
  • Active Since - timestamp when the service was last started

Detail form shows all of the above plus the raw systemctl status output for deeper diagnostics.

Docker Containers

Shows all Docker containers on the server, including containerized services such as Grafana, monitoring agents, and optional components.

Grid columns:

  • Name - the container name
  • Running - badge indicator (running or stopped)
  • Image - the Docker image in use
  • CPU - current CPU usage percentage
  • Memory - current memory usage
  • Created - when the container was created
  • Status - detailed status text (e.g., “Up 3 days”, “Exited (0) 2 hours ago”)

A Status filter lets you narrow the view to running, exited, or created containers.

Detail form shows container state, image, PID, start/finish timestamps, restart policy, command, networks, port mappings, volume mounts, and live CPU/memory usage.

Monitoring (Monit)

Provides an overview of services, filesystems, and system resources monitored by Monit. Monit continuously checks service availability and can automatically restart failed services.

Grid columns:

  • Name - the monitored resource
  • Status - badge indicator (up or down)
  • Type - resource type (Process, Filesystem, System, Network)
  • CPU - CPU usage (total including child processes, where available)
  • Memory - memory usage (total including child processes, where available)
  • Active Since - how long the resource has been monitored (uptime)

Filters for Type and Status let you narrow the view.

Detail form shows the full picture for each resource:

  • Status, monitoring status, and monitoring mode
  • Uptime, PID, CPU, and memory (total and process-only when they differ)
  • Port response time, space usage (for filesystems)
  • File descriptors, threads, load average, swap usage (for system resources)
  • Data collection timestamp

Best practices

  • Start here when something is broken. A stopped core service (PBX, Kamailio, database, Nginx) explains a great many symptoms at once - check it before digging into logs.
  • Watch memory and CPU on the Docker tab for containers that are slowly growing; catching a runaway container early avoids an out-of-memory event.
  • Trust Monit to self-heal, but investigate repeats. Monit can restart a failed service automatically; a resource that keeps going down points to an underlying problem worth fixing.
  • Use the detail form for depth. The raw systemctl status and container details give you the diagnostic context to hand off to support if needed.