Frequently asked questions

Free: up to 3 servers, 7-day retention, community support.

Pro: $3 per node per month with the first 3 nodes free (USD only). Unlimited servers, 90-day metric retention, unlimited notification channels, AI analysis (self-hosted Gemma 4), programmatic API access, email support. Example: 10 servers is $21/month (only 7 are charged).

All plans include the full 61-rule catalog and the MIT-licensed Crucible agent at no extra cost. See /pricing.

The first 3 servers stay active permanently (the Free quota is preserved on Pro accounts so service does not drop abruptly). Servers beyond 3 are disabled at the end of your current billing period (or at customer.created_at + 30 days, whichever is later). Disabled servers continue to ingest snapshots so historical data is preserved; they just stop firing notifications.

Warning emails fire when the payment method is removed, 3 days before disable, 1 day before disable, and at the moment of disable. Restoration is one click once a card is on file: Settings → Disabled servers → Restore all.

Proration. Add a server mid-month and you are charged proportionally for the remaining days. Remove a server and the next bill reflects the change.

Crucible runs on Linux. Tested distributions: Ubuntu 20.04 / 22.04 / 24.04, Debian 11 / 12, RHEL 8 / 9, Rocky Linux 8 / 9, AlmaLinux 8 / 9, Arch (rolling), Amazon Linux 2 and 2023. systemd plus kernel 4.18 or newer. x86_64 and aarch64.

Windows and macOS are not supported. For non-Linux hosts, push to the API directly with a custom collector.

Lightweight by design. Validation-fleet measurement on 2026-05-21 across 7 hosts shows a median 91 MB RSS idle (range 65 to 103 MB), near-zero CPU, and an fio delta under 1.5 percent. The binary is about 12 MB; logs rotate at 50 MB by default. Each push is 2 to 5 KB of compressed JSON; at the default 60-second interval, that is about 5 MB/day.

Crucible runs as the non-root glassmkr user. The install script provisions udev rules and group memberships that grant the user the necessary read access to /dev/ipmi0, raw block devices for SMART, and /proc / /sys. If you disable IPMI, SMART, and ECC monitoring, the agent works without those rules.

No. The agent initiates all connections outbound over HTTPS (port 443). Your firewall does not need to change.

Yes. If ipmitool is not installed or the BMC is not reachable, the IPMI module is silently skipped and the snapshot emits null for the IPMI fields. The dashboard renders that as "no signal (BMC not probed)". All other monitoring continues normally. See /docs/troubleshooting/ipmi.

sudo npm install -g @glassmkr/crucible@latest
sudo systemctl restart glassmkr-crucible

Pin a specific version with @glassmkr/[email protected]. Docker images are at ghcr.io/glassmkr/crucible:<version> and docker.io/glassmkr/crucible:<version>. Configuration in /etc/glassmkr/collector.yaml is preserved across upgrades.

# Stop and disable
sudo systemctl stop glassmkr-crucible
sudo systemctl disable glassmkr-crucible

# Remove the unit
sudo rm /etc/systemd/system/glassmkr-crucible.service
sudo systemctl daemon-reload

# Remove the package
sudo npm uninstall -g @glassmkr/crucible

# Remove configuration (contains the collector key)
sudo rm -rf /etc/glassmkr

Optionally delete the server from the dashboard to remove its stored metrics and free up a slot on your plan.

Metric data is stored on Glassmkr infrastructure in the EU. The operating company is a Czech sole-trader; all dedicated servers (including the database and the AI GPU) sit in DataPacket EU data centers, so the deployment inherits GDPR posture from the underlying provider. Data is encrypted at rest using AES-256 and in transit using TLS 1.3.

Glassmkr does not store raw system logs, process lists, or file contents. The collected data is numerical metrics (CPU, memory, disk, network counters) and hardware status identifiers (SMART, RAID, sensor readings).

Free: 7 days at full resolution.

Pro: 90 days. Data older than 7 days is downsampled to 5-minute resolution; data older than 30 days is downsampled to 1-hour resolution.

The server_unreachable rule fires after the server misses 2 consecutive check-ins (about 2 minutes at the default 60-second interval). Crucible buffers up to 60 snapshots in memory (about 1 hour at the default interval) and pushes the queue in order when connectivity is restored. If the buffer fills, the oldest snapshots are dropped first.

Yes. Pull metric data via the health history API. The response is JSON and can be piped into any analytics tool. For bulk exports, contact support for a CSV or Parquet dump of your account's data.

The Crucible agent is MIT-licensed and fully open source. The dashboard and alert evaluation engine are SaaS-only.

61 rules across 9 categories: storage, ZFS, filesystem, memory and CPU, network, hardware (BMC / IPMI), GPU, time and services, security and patching. 20 rules ship with deep FIX content (safe-mode, validation, rollback, impact); the rest are verified. Browse at /docs/rules.

Every alert has a priority from P1 (critical, immediate action required) to P4 (informational). Priority drives the badge color on alert cards and the emoji prefix in Telegram / Slack notifications. P1 indicates data loss or service outage; P2 indicates significant degradation; P3 is an early warning; P4 is a proactive recommendation.

Mute specific alert rules on a per-server basis from the server detail page or via the configuration file. Muted rules are not evaluated and do not fire notifications. Useful during maintenance windows, RAID rebuilds, or known-condition periods. Unmuting takes effect on the next ingest cycle. Alerts do not fire retroactively for conditions that occurred while muted.

On Pro, Glassmkr uses a self-hosted Gemma 4 model (running on a dedicated GPU server in the EU; no commercial LLM APIs) to analyze server health when alerts fire. The model reviews current metrics (including per-core CPU when available), recent trends, and the alert context to produce a one-sentence summary of the likely cause. The model is tuned to be conservative, to hedge, and to say "I don't know" when the signal is ambiguous. AI analysis is shown on the alert card and included in Telegram / Slack notifications.

When collectors.cpu.per_core: true (Crucible 0.3.0+), Crucible reports individual CPU core utilization in addition to aggregate metrics. Enables the per-core CPU chart in the expanded view and gives the AI analyzer per-core awareness. Useful for spotting single-threaded bottlenecks, core pinning issues, and uneven load. Increases data volume proportionally to core count.

Crucible monitors the host system, not individual containers. Container CPU and memory are visible in the host metrics as part of the total. Dedicated container and Kubernetes monitoring is on the roadmap.

If you run Crucible inside a Docker container, it needs access to the host's /proc, /sys, and device files via volume mounts. Installing on the host is simpler and more reliable.

Email + password, Google OAuth, and GitHub OAuth. Connect or disconnect OAuth providers under Settings → Account. There is no built-in TOTP today; rely on your OAuth provider's two-factor configuration if you sign in via Google or GitHub.

Yes. Token-bucket limiter with per-IP / per-key / per-account tiers plus per-endpoint sub-limits for write actions. Per-IP is 100 burst at 10/sec; per-key is 1000 burst at 100/sec; per-account is 5000 burst at 500/sec. Server registration, deletion, and key rotation each have their own hourly sub-limits. Ingest is rate-limited to one push per server per 55 seconds. See the API reference for the full table.

Email [email protected] with your account email and server ID. Include the output of sudo journalctl -u glassmkr-crucible --since "1 hour ago" --no-pager if the issue is agent-side.