sentry-relay
Overview
- Namespace:
sentry-relay - Purpose: Sentry Error Tracking Relay - PRODUCTION
- Age: ~219+ days (since March 2024)
- Status: Active - Error tracking relay service
- Workloads: 1 deployment (2 replicas) - Good HA
- Environment: PRODUCTION - Error event relay for Sentry
Architecture
Sentry Relay service for error tracking event forwarding:
- Relay Server: Event relay (2 replicas) - Good HA for events
Workload Categories
Relay Service (1 deployment with good HA)
| Name | Replicas | Status | Purpose |
|---|---|---|---|
| sentry-relay | 2/2 | Running | Sentry relay (Good HA) |
Services
| Name | Type | Cluster IP | Ports | Purpose |
|---|---|---|---|---|
| sentry-relay | ClusterIP | 10.8.24.212 | 3000, 3001 | Sentry relay service |
Quick Facts
- 2 replicas: Good redundancy for event relay
- Very stable: 219+ days since last update
- ClusterIP service: Internal only
- Event relay: Forwards errors to central Sentry
Production Considerations
Good HA Configuration:
- 2 replicas provide good redundancy
- Stateless service (easy to scale)
- Simple failure recovery
- Mature (~219+ days)
Troubleshooting
# Check relay status
kubectl get pods -n sentry-relay
# View logs
kubectl logs -f deployment/sentry-relay -n sentry-relay
# Check relay health
kubectl exec -it deployment/sentry-relay -n sentry-relay -- curl localhost:3000/healthz