Why Sluicio doesn’t have agents

Every monitoring agent you install costs more than the install. It’s a security review, a change ticket, an upgrade treadmill, and one more process that can take a box down at 2 a.m. Multiply that by every host in your integration landscape, and “just install our agent” becomes a project of its own — before you’ve monitored anything.

We took the opposite bet: Sluicio reads the OpenTelemetry signals your services already emit. No proprietary agent, no rip-and-replace. If you can point an OTLP exporter at us, you’re streaming.

exporters:
  otlphttp/sluicio:
    endpoint: your-tenant-ingest.sluicio.com:4318   # your Sluicio ingest endpoint
    headers:
      authorization: "Bearer ${env:SLUICIO_INGEST_TOKEN}"

service:
  pipelines:
    traces:
      exporters: [otlphttp/sluicio, otlp/existing]  # runs alongside what you have

Note that second exporter: Sluicio runs next to your existing stack, not instead of it. The same signals keep feeding Grafana, Datadog, or your own backend in parallel. There’s nothing to migrate, nothing held hostage — and if you ever want to leave, leaving is deleting a line. We think a monitoring tool should earn its place in your pipeline every day, not lock the door behind you.

That’s the whole idea: standard signals, your infrastructure, failures ranked first.

—

Sluicio is in private beta — we’re onboarding teams in small cohorts. Join the waitlist, or email support@sluicio.com about a design-partner pilot if you’d rather skip the line.