Monitoring

Public-Safe Status Dashboard

How the Lumen Tools page shares operational status without publishing secrets, logs, prompts, or private infrastructure details.

Read the notes →Open Lumen Tools

Publishing status without giving away the keys

The Lumen Tools dashboard exists to show that the lab is alive while keeping the dangerous details out of public view.

Shown publicly

Gateway/service status.
CPU, memory, disk, and uptime summaries.
Scheduled job names, modes, and run status.
Sanitized timestamps and health indicators.

Not shown

Secrets, tokens, and environment variables.
Private prompts or message content.
Raw logs and command output.
Internal admin endpoints or credentials.

Why it matters

Monitoring is more useful when it can be glanced at safely. A public page should help humans understand status without helping attackers understand the network.

The pattern

Collect

Gather status locally from trusted scripts and services.

Sanitize

Remove private paths, raw logs, credentials, prompts, and sensitive configuration.

Publish

Write a small public JSON snapshot and render it on a polished page.

Verify

Check the live page and raw feed to make sure the output is safe and useful.

Live example: Lumen Tools is the current public-safe status dashboard for the lab.