Question 1

Does Ana support self-hosted Sentry?

Accepted Answer

Yes. The connector supports both Sentry.io cloud and self-hosted Sentry instances. An admin simply whitelists the self-hosted Sentry domain in the TextQL admin console and provides an auth token. Ana can then query any project the token has access to.

Question 2

Can Ana read Sentry release health?

Accepted Answer

Yes. Sentry's release health data including crash-free sessions, adoption, and regressions is fully accessible through the API. Ana joins release health with warehouse deploy and business metrics to measure the real impact of a release.

Question 3

How are Sentry tokens secured?

Accepted Answer

Auth tokens are encrypted at rest in TextQL's credential vault and injected by our egress proxy at the network layer. Ana's Python sandbox never sees the raw token value. Tokens can be rotated any time from the TextQL admin console without changing prompts.

Question 4

Can I use a scoped Sentry token?

Accepted Answer

Yes, and we recommend it. Sentry lets you create tokens with specific scopes per organization or project. Create a dedicated read-only token for TextQL limited to the projects you want Ana to analyze. Admins can store multiple tokens for separation of duties.

Question 5

Does Ana see Sentry PII?

Accepted Answer

Only if Sentry is configured to capture PII in its events. We recommend scrubbing PII at the Sentry SDK level rather than relying on Ana to filter it. Admins can also restrict the TextQL token to read-only metadata scopes to minimize PII exposure risk.