Integration monitoring · Built on OpenTelemetry
Catch every failure before it catches you.
Stop debugging in log files. Sluicio shows you exactly what every integration, service, and message is doing — so you find the failure before your users do.
Free Community Edition · Self-hosted in minutes · Built on OpenTelemetry — no proprietary agents
What you can finally do
Three things that used to take a war room.
Sluicio reads all three OpenTelemetry signals — traces, metrics, and logs — and gives back the actual answer, not another dashboard. Built by people who've spent too many nights in #incident-prod.
Traces
Follow one message hop-by-hop across every service, queue, retry, and external call.
Metrics
Throughput, success rate, latency, queue depth — for every integration, in real time.
Logs
The actual error text, the actual payload, the actual line — attached to the message it came from.
01 · Overview
See the entire flow at a glance.
One screen that says "you're fine" or "this one needs you." Every integration, every service, every message bus — grouped the way your team thinks about them.
- Live KPIs — throughput, success, latency, queue depth. Real numbers, no marketing colours.
- Severity-first ordering — failures float up. Healthy stuff stays out of your way.
- 30-second read — a new on-call engineer knows the state of the world before their coffee.
| Integration | p95 | Status |
|---|---|---|
| Stripe payouts | 182ms | Failed |
| Order queue | 240ms | Degraded |
| Shopify orders | 96ms | Healthy |
| Netsuite sync | 120ms | Healthy |
02 · Message search
Find any message in seconds.
A customer asks "where is order #1323?" — and you answer in 10 seconds, not 10 minutes. Search across payload, headers, and metadata. Matched fields surface inline.
- Full-payload indexing — search JSON, XML, EDI, fixed-width. Type the value, see the message.
- Matched fields inline — no clicking into every row to find why it matched.
- Replay from any point — kick a stuck message back into the pipeline with one click.
03 · End-to-end trace
Trace a failure end-to-end.
One message, one timeline, every hop. From the file drop, through the queue, through three services, out to the third-party API — including the retry attempts no one usually sees.
- Causal timeline — every transformation, queue, retry, and external call in order.
- Payload at every step — see exactly what changed, before and after.
- Drop the screenshot in your ticket — and your support team is done arguing.
OpenTelemetry-native
If your stack speaks OTel, Sluicio reads it.
No proprietary agents, no scrapers, no "connector marketplace." Sluicio consumes the OpenTelemetry traces, metrics, and logs your services are already emitting — and reconstructs the integration view on top.
Concretely, things you're probably already running.
All of these have OpenTelemetry auto-instrumentation or first-class SDK support today. The OTel registry is large — this is just the slice that shows up in integration work most often.
Languages & runtimes
- Java (JVM agent)
- .NET (auto-instrumentation)
- Node.js
- Python
- Go
- Ruby
- PHP
- Rust
Brokers & streaming
- Apache Kafka
- RabbitMQ
- AWS SQS / SNS
- Azure Service Bus
- Google Pub/Sub
- Apache Pulsar
- NATS
- JMS / Jakarta Messaging
Databases & stores
- PostgreSQL
- MySQL · MariaDB
- SQL Server
- Oracle
- MongoDB
- Redis
- Cassandra · ScyllaDB
- Elasticsearch · OpenSearch
iPaaS & workflow
- Apache Camel (native OTel)
- MuleSoft (OTel module)
- Boomi (OTel exporter)
- Spring Integration
- Apache NiFi
- Apache Airflow
- Temporal
- AWS Step Functions
HTTP & RPC frameworks
- Spring Boot
- ASP.NET Core
- Express · Fastify · NestJS
- Django · FastAPI · Flask
- Gin · Echo · Fiber
- gRPC (all langs)
- GraphQL (Apollo, etc.)
- Rails · Laravel
Cloud & serverless
- AWS Lambda
- Azure Functions
- Google Cloud Functions
- AWS API Gateway
- Kubernetes Jobs & CronJobs
- Knative
- AWS Kinesis
- Cloudflare Workers
The standard
Built on OpenTelemetry, on purpose.
Sluicio reads OpenTelemetry — the CNCF observability standard. If your team is already on it, you're done in an afternoon. If you're not, this is the right reason to make the move: the telemetry you emit for us will feed everything else too, forever.
What it is
OpenTelemetry is the open, vendor-neutral standard for collecting traces, metrics, and logs. CNCF-graduated. Backed by every major cloud and observability vendor.
What we need from you
Your services emit OTel — via auto-instrumentation (already on in most modern stacks) or a few lines of SDK. Point your OTLP exporter at Sluicio and you're streaming. No agents to deploy.
What you get back
Zero lock-in. The same telemetry can feed Datadog, Grafana, Honeycomb, or your own backend in parallel. You're investing in your stack, not in us.
Already on Prometheus? Keep it.
The OpenTelemetry Collector scrapes any Prometheus endpoint and re-emits it as OTLP — so your existing JMX exporters, postgres_exporter, Micrometer setup, and ASP.NET metrics keep working. Sluicio reads all three OTel signals — traces, metrics, and logs — because a single signal can't answer everything. Prometheus covers the metric side; OTel rounds it out with the rest.
Getting started
From your stack to insight — in four steps.
No rip-and-replace, no proprietary agents. Sluicio reads the OpenTelemetry your systems already speak — so first insight is an afternoon away, not a quarter.
-
01
What you have today
Services, message brokers, and the flows between them. Most already emit OpenTelemetry — or can with auto-instrumentation in an afternoon.
-
02
Send it through your Collector
Add Sluicio as an OTLP exporter in your existing OpenTelemetry Collector. No proprietary agents, no rip-and-replace.
-
03
Assess in Sluicio
Your raw spans, metrics, and logs assemble into live integration health — topology, per-flow status, end-to-end traces, and alerts.
-
04
Immediate gains
Catch the break before your users do, and pinpoint root cause in a single trace — from day one.
Not sure where you stand with OpenTelemetry? Pick your starting point:
- Add an OTLP exporter for Sluicio to your Collector config.
- Reference it in your traces, metrics, and logs pipelines.
- Reload the Collector — your integrations show up in Sluicio.
exporters:
otlphttp/sluicio:
endpoint: https://otlp.sluicio.example:4318
headers:
Authorization: "Bearer ${env:SLUICIO_TOKEN}"
service:
pipelines:
traces:
exporters: [otlphttp/sluicio]Recommended: run a Collector. It is far easier to control which data goes where — filter, batch and route in one place — so you never ship telemetry you do not need.
- Deploy an OpenTelemetry Collector — one container is enough to start.
- Point your services at the Collector, then export from the Collector to Sluicio over OTLP/HTTP.
- Traffic starts flowing — no code changes to your services.
OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf
OTEL_EXPORTER_OTLP_ENDPOINT=https://otlp.sluicio.example:4318
OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer <your-token>"Free kickoff: book an OpenTelemetry session with us — free of charge — and we'll help you get going: map your stack, pick the right auto-instrumentation, and get the first signals flowing. Deeper hands-on onboarding and instrumentation work are available as paid services.
- Add OpenTelemetry auto-instrumentation to your services — a language agent, no code changes for most stacks.
- Run a Collector to receive and forward the telemetry.
- Point it at Sluicio. Want a hand? We help you onboard OTel.
# Java, for example — auto-instrument, then export over OTLP/HTTP
OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf \
OTEL_EXPORTER_OTLP_ENDPOINT=https://otlp.sluicio.example:4318 \
OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer <your-token>" \
java -javaagent:opentelemetry-javaagent.jar -jar app.jarFor the whole team
Different jobs, same screen.
Sluicio is the one place where ops, dev, support, and engineering management read the same truth — without each team running a parallel script.
Integration developers
“I built it. I can finally see what it's actually doing in prod.”
Inspect payloads at every hop. Reproduce a failed message locally with one click. Stop adding log lines just to debug.
Operations / SRE
“The right alert, with context — instead of a wall of false positives.”
Alert on what matters: failed retries, growing backlogs, missed SLAs. Page once with everything the on-call needs.
Support engineers
“Where is order #1323? — answered in 10 seconds.”
Search by any field. Read the whole story without escalating. Close the ticket without booking an engineer.
Engineering managers
“A 30-second read on whether things are OK.”
One screen for the standup. Trend lines for the quarterly. Hard numbers when procurement asks what the integrations are doing.
Pricing
Free to self-host. Pay only for the enterprise layer.
The full product is free and self-hosted — no limit on integrations, users, or data. The Enterprise Edition adds SSO, RBAC, audit, and support, priced simply by number of integrations.
- Community Edition — free forever, self-hosted, with no limits
- Enterprise adds SSO, advanced RBAC, audit log, MFA, and retention controls
- Priced by integrations — never per user, per GB, or per host
Prices are an early draft, still under review.