Skip to main content
Use the @bijection/connectors/sentry entrypoint to declare Sentry resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Issues

pull: Issue measurements with signed webhook hints

The following example matches configuration webhooks.

Configuration: standard

Case: sentry/issues/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: sentry. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: issues
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Configuration: webhooks

Case: sentry/issues/pull/webhooks. Connection and resource configuration are declared by this exact case. Credential kind: sentry. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: issues
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Project events

pull: Project error events

The following example matches configuration standard.

Configuration: standard

Case: sentry/events/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: sentry. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: events
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Event-count buckets

buckets: Error counts with read-back spacing

The following example matches configuration standard.

Configuration: standard

Case: sentry/stats/buckets/standard. Connection and resource configuration are declared by this exact case. Credential kind: sentry. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: buckets
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. A read-only measurement source. Nothing here resolves, merges, assigns or deletes an issue. The connection selects the organization’s region host (region, for example us for https://us.sentry.io) and holds a sentry bearer credential (sentry.credential). Bindings name the organization slug and, for events, the project slug. Identity is the organization id. issues.pull lists issues matching a Sentry query (is:unresolved by default) by the Link cursor. Sentry always writes a rel="next" member, even with nothing behind it; results="false" ends the walk. Status is Sentry’s own field and is never derived from counts: an issue’s status did not follow its events. Sentry offers no watermark, so a pass claims no coverage and an issue leaving the query is not withdrawn. With updates: "webhooks", an internal-integration delivery verified as HMAC-SHA256 in hex over the raw body (sentry-hook-signature), identified by request-id, requests a point read of data.issue.id. The timestamp travels in a separate sentry-hook-timestamp header the signature does not cover, so it bounds nothing and a delivery proves a refresh hint. events.pull lists one project’s error events by the Link cursor. This endpoint was not exercised by the probe; it is declared from Sentry’s published API. stats.buckets reads error-event counts from events-stats over the errors dataset, an exact count over stored events. The interval is a request, not a contract: interval=1s silently returned hour buckets. Each bucket therefore carries spacingSeconds read back from the response beside the requestedInterval. Retention is not stated; Sentry refuses a period past it. Nothing here has run against Sentry or been qualified.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.