SpanSliceSign in

Send the spans that explain things. Archive the rest.

SpanSlice decides inside your services which traces reach your observability vendor, and keeps everything else in storage you own.

  1. GET /checkoutrootsent: root
  2. auth.verifyarchived
  3. cart.loadarchived
  4. cache.getarchived
  5. db.query cartsarchived
  6. payments.chargeslowsent: slow
  7. POST api.stripe.comerrorsent: error
  8. db.insert ordersarchived
  9. queue.publisharchived
Sent to your vendorArchived to your bucket
Rules at the source
Keep, drop or redact spans inside the SDK, before they're exported and billed.
Changes without a deploy
Edit a rule once and running services pick it up in seconds, per service and environment.
Nothing thrown away
Spans you don't send are archived to your own bucket, ready when an incident needs them.
Built on OpenTelemetry
Works with the instrumentation you already have and the vendor you already use.