Skip to content

Monitoring Muppy Enterprise

This page describes how to check that the components of a Muppy Enterprise installation are running, from the Muppy Bootstrap server.

Four checks, in the order that isolates a problem fastest:

  • the Muppy user interface,
  • Muppy's Traefik reverse proxy,
  • the Muppy application server,
  • Muppy's database server.

The Bootstrap server is what makes this possible: it manages the Muppy server as one of its Hosts, so it can inspect it even when the instance being checked is the one that is down.

1. The Muppy user interface

Open Muppy's public URL and check that it displays and responds normally.

2. The Traefik reverse proxy

  1. Open the Muppy Bootstrap server's interface.
  2. Open the Host of the Muppy server you are checking.
  3. On the Services tab, in the Systemd Units group, open the service unit mpy_traefik.service.
  4. Refresh its status: it must be active, loaded and enabled.
  5. Read its log, retrying to reach Muppy in parallel, and check that no error appears.

3. The Muppy application server

  1. Open the Muppy Bootstrap server's interface.
  2. Open the Host of the Muppy server you are checking.
  3. On the LXD tab, open the LXC that runs Muppy.
  4. On its Services tab, check the two application services — the GUI unit and the cron unit, named mpy_*_appsrv_*_gui.service and mpy_*_appsrv_*_cron.service.

For each of them:

- refresh the status: it must be **active**, **loaded** and **enabled**;
- read the log — for the GUI unit, retry reaching Muppy in parallel — and check that no
  error appears.

4. The database server

  1. Open the Muppy Bootstrap server's interface.
  2. Open the Host of the Muppy server you are monitoring.
  3. On the PostgreSQL tab, open the database cluster.
  4. Refresh its status and check that the cluster is Online.
  5. If it is not, open the cluster's Systemd Unit and check its status and its log.

See Cluster Control & Status for what the cluster states mean and how to act on them.