Changelog
Release notes for Sluicio — a feature overview of the 1.0 release, with detailed per-release changes from 1.0 onward.
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).
Unreleased
Section titled “Unreleased”Nothing yet — changes land here as they’re made, then move into a dated release section.
1.0-rc — 2026-06-28
Section titled “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
Section titled “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
Section titled “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
Section titled “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
Section titled “Integrations & message flow”- Model integrations with per-integration messages, logs and errors, a flow view, and attribute key/value filtering.
Reliability
Section titled “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
Section titled “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
Section titled “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
Section titled “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
Section titled “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)
Section titled “Sluicio Enterprise (license-gated)”- Advanced RBAC (group access policies), audit log, and long retention. OpenID Connect SSO is planned — see Identity & SSO.
Deploy
Section titled “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.