Sluicio v0.11.56

Multi-architecture images start here: every image now publishes linux/amd64 and linux/arm64 in one manifest.

Images now run natively on arm64

Sluicio published amd64 only, so Graviton, Ampere and Apple silicon either refused the image or ran it under emulation. Every image — cell-api, cell-ingest, controlplane, frontend and the demo seeder — now ships both architectures in a single manifest, so docker pull and helm install resolve the right one with no per-architecture tags and no chart changes.

Nothing about how you deploy changes. ghcr.io/sluicio/cell-api:v0.11.56 simply works on both.

A system watched only by its own health checks no longer reads "Quiet"

If a system's health is defined entirely by checks bound to it — with no member services, because one runtime emits several systems' telemetry and is told apart by attribute — the system reported Quiet, meaning nothing is watching it.

It was more than a label. A metric check on a system with no members never evaluated at all: the scope resolved to zero services and returned no data, so the check never fired, never resolved, and the system sat on "Quiet" while looking configured.

That behaviour was designed for integrations, whose membership is reconciled in the background — there, an empty set usually means "not ready yet". System membership is attached by hand, so empty is a deliberate choice, and often the correct one. Systems now evaluate such checks against the rule's own criteria; integrations are unchanged.

Two details worth knowing:

• Metric and log checks work on a memberless system, because each carries its own narrowing — a metric rule names a metric, a log rule sets a severity floor. The system page states this, since a metric check with no attribute filters then watches every service you can see.
• Response-time and low-traffic checks still need members. They carry no criteria of their own, so "unscoped" would mean the whole cell, and "p95 across everything" is not a statement about a system.

A passing check now reads ok; a firing one still reads unhealthy and outranks everything. An unhealthy member service still makes the system unhealthy regardless. "Quiet" now means what it says: nothing is watching.

Health checks on the same metric are told apart

Three checks on one metric that differed only by attribute filter and by what they governed rendered as three identical rows — same name, same condition, same badge, three "remove" buttons and no way to know which was which. New checks are named <metric> alert by default, so they all start out identical.

Each row now shows its attribute filters, and the service, integration or system whose health it defines — by name. Checks that only notify say so.