Skip to content

Monitoring and Services

Inspect resource metrics and safely control managed services.

1Overview

Monitoring shows host health and service-level signals; Services exposes start, stop, restart, and enable controls for managed daemons such as web, database, mail, and DNS services.

Monitoring and Services in the administrator panel. Account names, domains, and addresses are examples. Available controls depend on your package and server configuration.
Services page listing server daemons, their running or stopped states, and available service management actions.

Monitoring and Services in the administrator panel. Account names, domains, and addresses are examples. Available controls depend on your package and server configuration.

2Before you begin

Administrator actions can affect multiple customer accounts and server services. This is an advanced task; schedule it carefully and keep a rollback path.

3Step-by-step workflow

Open Monitoring to identify the affected resource, then open Services, choose the exact service, and use Restart for a healthy configuration reload or Start for a stopped service. Confirm the final Running status and test the dependent panel function.

  1. Open Monitoring to identify the resource or service involved in the reported problem.
  2. Select an appropriate time range and compare CPU, memory, storage, network, and process activity where shown.
  3. Note the incident time and correlate the reading with a website deployment, backup, or scheduled task.
  4. Open Services and read the status and explanation for the specific service.
  5. Expand additional services to distinguish installed, on-demand, stopped, and unconfigured components.
  6. Use Start or Restart only for the identified service and wait for the action result.
  7. Test the dependent website, DNS, email, database, or panel function.
  8. Review the related log if the service stops again instead of repeatedly restarting it.

4Practical example

Example: a backup can temporarily increase disk activity and CPU use. Compare the monitoring period with the backup job before treating the load as a website fault.

5Verify the result

Validate the outcome from the affected account or an independent client connection, not only from the administrator screen.

  1. Confirm the service reports Running.
  2. Test the dependent panel, website, database, mail, or DNS function from a client connection.

6Common problems and what to check

A service is on demand: read its explanation before trying to keep it running permanently.

A service fails to start: inspect the configuration and service log before restarting again.

Charts look stale: check the selected time range, refresh interval, and latest recorded sample.

7Security, impact, and rollback

Stopping MySQL can make the panel unavailable because account data is stored there. Keep a second SSH session open for recovery and never stop a service without knowing its dependencies.

Related guides

Server PHPManage installed PHP runtimes and safe server-level configuration.Root TerminalRun carefully scoped server commands from the administrator panel.See all guides in Administrator panel

Still need a hand?

Get help with your plan, website, or hosting through your client area.

Open client area