Skip to main content
Sentry is a read-only DevTools panel, not an issue destination. A workspace owner connects one Sentry organization and project; current workspace members, including viewers, can read the returned event summaries on a capture. Public shares cannot use the Sentry panel, and Sentry is intentionally omitted from Send to app.

​
Requirements and connection

Tekma supports Sentry.io cloud and one configured project. OAuth is available only when the deployment has configured a Sentry client; otherwise use Use a token instead with a read-capable token. The configured OAuth/token scopes are org:read, project:read, and event:read. Provider retention, plan limits, project permissions, and event availability still apply.
  1. Open Settings → Integrations and choose Connect beside Sentry.
  2. Choose Continue to Sentry when offered, or choose Use a token instead.
  3. Enter Organization slug and Project slug. These identify the backend project whose events workspace members may read; they are not per-capture fields.
  4. Choose Connect Sentry. Tekma verifies the organization/project pair before the row becomes Connected.
Use Manage to select another project while keeping the authorization. Tekma has no self-hosted or regional endpoint field and does not promise cross-project queries. Disconnecting stops later reads.

​
Read events

  1. Open a capture and open DevTools.
  2. Select the Sentry tab when it is available. Tekma starts with the stored recording-start timestamp; when no start is stored, it uses the capture’s capturedAt timestamp. It never uses upload or database-creation time.
  3. Choose the dataset Errors or Logs. Search is a literal phrase filter. Set Environment when needed; an explicitly empty environment searches all environments.
  4. Adjust the UTC time window or use the default ±5 minutes. A custom positive window cannot exceed 24 hours. Use pagination controls to read another page.
  5. Select an event link to open that event in Sentry. The event timestamp is a backend time, not a video playhead position; temporal proximity does not prove causation.
Tekma fetches results on demand. It projects only event ID, timestamp, message/title, severity and a Sentry link. Raw request bodies, user records, stack traces, arbitrary provider fields and credentials are not returned. Results are not persisted into the capture, public share, search index, or AI report. Sentry context is also not added to a destination issue or Slack message.

​
Troubleshooting

If the Sentry tab is empty, verify the configured project, token/OAuth scopes, event retention, environment, and time range. Select Errors versus Logs deliberately and widen the range within the 24-hour limit. A capture’s video timeline and Sentry’s event timestamps are separate. If an OAuth grant covers an unavailable site or the project was renamed, use Manage or reconnect. Self-hosted Sentry, regional endpoints, and cross-project browsing are outside this integration.