Changelog

Release notes for Sluicio. The 1.0 release is summarised below as a feature overview. From 1.0 onward, each release records its individual changes (Keep a Changelog style).

v0.11.40 — 2026-07-25

Added

• Production-ready Kubernetes/OpenShift Helm chart. The cell chart (deploy/helm/cell) now covers Enterprise installs end to end: one chart for both editions (a license Secret activates Enterprise at runtime, unlicensed runs Community Edition), values variants for bundled databases, external databases, and OpenShift (restricted-v2 SCC clean, Routes), plus new opt-in networkPolicy and podDisruptionBudget hardening. The chart is validated in CI across all three variants and smoke-tested in kind; releases after this one also publish it to oci://ghcr.io/sluicio/charts/sluicio-cell. See Self-hosted on Kubernetes / OpenShift.
• Outbound event subscriptions. Sluicio can now push its domain events — alert firings and resolutions, error-notifier pages, service discoveries, and every audited configuration change — to your own platform (Azure Event Grid, AWS EventBridge, n8n, an internal bus) instead of being polled. Subscriptions live on the Developers page: glob filters over reverse-DNS event types, team or org scope, delivery over webhook channels in CloudEvents 1.0 or flat JSON, signed and at-least-once. Each subscription keeps a delivery ledger — state, attempts, last error per event — for about three days. See Event subscriptions.

Changed

• Settings → System is now five sub-tabs. The single System page is reorganized into General (environment, ingest URL, treat HTTP 5xx as errors, disallow org-wide service accounts), Email (SMTP), Security (MFA policy), Notification templates, and Announcements. Deep links address a sub-tab directly with ?tab=system&sub=email|security|templates|announcements.
• One surface for default alert formatting. The cell-wide Alert email template card on Settings → System has been folded into the org notification-templates set — now Settings → System → Notification templates — so email subject/body and Slack title/body are edited in one place, overridable per team and per rule. An existing cell-wide email template is migrated into the org default automatically on first boot after upgrading. See Notification templates.

v0.11.39 — 2026-07-24

Fixed

• Maintenance windows now cover stuck messages. A flow-completion (stuck-message) firing during an active maintenance window no longer pages its channels — it’s recorded as suppressed like any other alert, and pages when the window ends if the trace is still stalled. Previously it paged straight through the window, then paged a second time when the window closed. See Alerting.

1.0-rc — 2026-06-28

Sluicio 1.0 is an integration-monitoring platform built on OpenTelemetry. You point any OTLP source at it and get discovery, tracing, message-flow tracking, and alerting with nothing to define up front. The first release delivers:

Ingestion & instrumentation

• OTLP/HTTP ingestion of traces, metrics and logs, authenticated with per-organization ingest keys (mint, rotate, revoke).
• Works with any OpenTelemetry SDK or Collector — see Point the Collector at Sluicio and Instrument a service.

Services, systems & topology

• Automatic service discovery from OTLP resource attributes.
• Group services into service types and systems, with a live topology / dependency map.

Traces & search

• Trace waterfalls for any request, end to end.
• Global search across traces and spans by service, span name, status, or any attribute.

Integrations & message flow

• Model integrations with per-integration messages, logs and errors, a flow view, and attribute key/value filtering.

Reliability

• Errors surfaced per service and integration.
• Continuous success rate / health.
• Flow-completion rules that catch messages which started but never finished — surfaced as stuck messages.

Metrics, logs, dashboards & alerts

• Browsable metric catalog with per-chart transforms (raw / increase / rate).
• Logs searchable alongside the traces they belong to.
• Dashboards (including system-health cards) and a “since last visit” activity digest.
• Alert rules delivering to email and webhook channels.

Organise

• Tags, facets and metadata fields for the groupings your team uses.
• Monitoring templates — built-in per-kind templates plus user-defined ones.

Programmatic & MCP access

• A REST API, and a remote MCP endpoint so an MCP client (or AI assistant) can query services, traces, errors and metrics.

Security & access

• Email + password accounts with Admin / Editor / Viewer roles.
• Multi-tenant isolation — every query is scoped to an organization.
• Ingest keys and API/MCP tokens stored as SHA-256 hashes; see the Security model.

Sluicio Enterprise (license-gated)

• Advanced RBAC (group access policies), audit log, and long retention. OpenID Connect SSO is planned — see Identity & SSO.

Deploy

• Self-hosted, single box or split, with bounded retention so volume plateaus. Size it with the capacity planner.

For what all of this means in practice, see What you get from your telemetry.