Epure
Star on GitHub
Guide

Envelope items: what Epure keeps and drops

Table first: exceptions keep; transactions, replay, and profiling drop. Verify a known event. Partial wire honesty.

EpureUpdated

On this pageShow
  1. Keep vs drop
  2. Keep path
  3. Drop path
  4. Verify steps
  5. Questions

Start with the keep/drop table. Then verify one known exception.

Keep vs drop

Envelope intent vs Epure behavior

Exception / error event

Epure behavior
Keep path, then issue + stack

Transaction / spans (APM)

Epure behavior
Drop / ignore (out of scope)

Session replay

Epure behavior
Drop / ignore

Profiling

Epure behavior
Drop / ignore
DimensionEpure behavior
Exception / error eventKeep path, then issue + stack
Transaction / spans (APM)Drop / ignore (out of scope)
Session replayDrop / ignore
ProfilingDrop / ignore

Authoritative detail: Envelope API. Do not invent item-type rows beyond docs.

Keep path

  • Official Sentry SDK with Epure DSN.
  • captureException / unhandled exception integration.
  • HTTP 202 on accept (subject to spike valve / caps: Spike valve).
  • Grouped issue in UI.

Drop path

If you leave tracesSampleRate, replay, or profile rates enabled, the SDK may still ship items Epure will not surface as product features. Set them to 0 to save bandwidth and avoid confusion.

Verify steps

  • Confirm project id in DSN.
  • Send only a known exception.
  • Confirm Issues row: Verify.
  • Optionally send a transaction-only payload in staging and confirm it does not become an APM view (Epure has none).

Questions

Can I just change the DSN?
Yes for exceptions. No for replay, APM, or profiling product parity.
Is store legacy still accepted?
See current Envelope API / errors docs for store vs envelope. Prefer envelope on modern SDKs.
Does drop mean HTTP 4xx?
Not necessarily. Many out-of-scope items are ignored while exception items in the same request may still accept. Trust docs + Verify, not assumptions.