Install and operate

Health and diagnostics

After the install, Lagoria Control is your window into the environment. Start it whenever you want to check on Lagoria, then close it again.

Start Lagoria Control#

Run the same command as for the install, from the same working folder, and open the link it prints. Your settings are remembered; only the AWS access has to be connected again, because credentials are never stored.

cd ~/lagoria-control
docker run --rm -it -p 127.0.0.1:8080:8080 \
  -v "$HOME/.aws:/home/lagoria/.aws" -v "$PWD:/work" \
  lagoria-control:<version>

For health and diagnostics, read-only credentials are enough. Install and upgrades need administrator rights.

The Overview#

The Overview shows the installed version, the version of the image you are running, Lagoria's address, and a diagram of its parts. Each part is checked on its own, so one problem never hides the others.

State	Meaning
Healthy (green)	Working as expected.
Needs attention (amber)	Working, but something is worth a look, such as failed ingestion jobs or a custom domain that is not live yet.
Failing (red, pulsing)	Not working. The lines into it turn red so you can see what depends on it.
Idle (grey)	Switched off or parked on purpose: search scaled to zero, or a graph stopped out of hours. Not a fault.

Select a part to see its details and numbers.

Overview with the API failing and AI needing attention; the API details panel shows HTTP 502 and 37 errors in the last hour — Two parts need attention. The API is failing: its details show the health endpoint answering HTTP 502.

Choose Refresh to check again. When something is failing and the reason is not obvious, run diagnostics and send us a support bundle.

Diagnostics#

Diagnostics → Run checks runs the same checks as before an install: credentials, region, Bedrock model access, identity provider and the installation itself.

Support bundle#

Download support bundle builds a zip file with what we need to help. Open it and review it before you send it to us.

Included	Never included
Versions; settings, with email addresses shown as `<redacted>@domain`; check results; component health; failed deployment events; recent error lines from the last hour, with emails and tokens redacted; Lagoria Control's activity log.	Secret values, request contents, document contents.

Configuration#

Change the environment or sign-in settings, or store a new client secret. Changes are saved here and take effect on the next deploy. This is also where you find the redirect URI to register with your identity provider.

Activity#

Every action taken through Lagoria Control (connecting, storing secrets, deploys and their outcome) is listed, newest first. The same log is kept in audit.log in your working folder, for your change records.