Migrate from Sentry SaaS
هذا المحتوى غير متوفر بلغتك بعد.
Migrate from Sentry SaaS to ɳSentry
Section titled “Migrate from Sentry SaaS to ɳSentry”ɳSentry offers the same observability capabilities as Sentry — uptime monitoring, error tracking, incident management — but self-hosted on your infrastructure.
Why Migrate
Section titled “Why Migrate”| Aspect | Sentry Cloud | ɳSentry Self-Hosted |
|---|---|---|
| Pricing | Per-event billing | Fixed monthly ($0.99/mo bundle) |
| Data residency | Sentry servers | Your infrastructure |
| Vendor lock-in | Export limited | Full data ownership |
| Compliance | Standard SLAs | Customizable, HIPAA-ready |
| Extensibility | Limited | Unlimited (Go plugins) |
Migration Path
Section titled “Migration Path”Phase 1: Parallel Running (Week 1)
Section titled “Phase 1: Parallel Running (Week 1)”Keep Sentry running while ɳSentry stabilizes.
- Install ɳSentry bundle
- Configure SDKs to send to both endpoints (Sentry + ɳSentry)
- Verify data flow into ɳSentry dashboard
- Monitor parity across error counts + alert accuracy
Phase 2: Traffic Cutover (Week 2)
Section titled “Phase 2: Traffic Cutover (Week 2)”Shift SDKs to ɳSentry.
// Before: Sentry onlySentry.init({ dsn: "https://key@sentry.io/..." });
// After: ɳSentry onlySentry.init({ dsn: "https://key@sentry.yourdomain.com/..." });Update all app SDKs:
- Web (JavaScript/TypeScript)
- iOS (Swift)
- Android (Kotlin)
- Backend (Go, Python, etc.)
Phase 3: Validation (Week 3)
Section titled “Phase 3: Validation (Week 3)”- Verify all errors flowing to ɳSentry
- Test alerting (Slack, email, PagerDuty integration)
- Confirm incident workflows
- Check SLO calculations
Phase 4: Cleanup (Week 4)
Section titled “Phase 4: Cleanup (Week 4)”- Archive old Sentry projects
- Cancel Sentry subscription
- Document runbooks for ɳSentry
- Train team on status page + incident management
Data Export from Sentry
Section titled “Data Export from Sentry”Before canceling, export your history:
# Export error events (requires Sentry API key)curl -H "Authorization: Bearer YOUR_SENTRY_TOKEN" \ https://sentry.io/api/0/organizations/YOUR_ORG/events/export/ \ > sentry-export.json
# Import into ɳSentry via bulk APIcurl -X POST https://sentry.yourdomain.com/api/errors/import \ -H "Authorization: Bearer NSENTRY_TOKEN" \ -d @sentry-export.jsonPricing Comparison
Section titled “Pricing Comparison”Sentry Cloud:
- $29/mo (base) + $0.50–$2.00 per 1M events
ɳSentry Self-Hosted:
- $0.99/mo (bundle) + infrastructure cost (~$20–50/mo on Hetzner CX23)
- Total: ~$20–51/mo (vs Sentry’s $100+/mo for typical usage)
Support During Migration
Section titled “Support During Migration”- Documentation: https://docs.nself.org/nsentry
- Issues: GitHub nself-org/cli (tag
nsentry) - Chat: chat.nself.org (ɳChat app, included in ɳSelf+ bundle)
See also: Architecture · Plugins · API