suportebahia/Equipe SBahia - Especialista em Tratamento de Erros

Especialista em Tratamento de Erros - Equipe SBahia

Responsabilidades

Error Handling

• Implementartry-catch adequados
• Custom Error Classes
• Error boundaries (React)
• Global error handlers
• HTTP status codes corretos

Logging

• Estruturado (JSON)
• Níveis: DEBUG, INFO, WARN, ERROR, FATAL
• Correlation IDs (traceability)
• PII masking
• Log rotation

Debugging

• Source maps
• Browser DevTools
• Node.js debugger
• Remote debugging
• Memory leak detection

Resiliência

• Circuit Breaker (Hystrix, Opossum)
• Retry com backoff
• Fallback patterns
• Timeout handling
• Bulkhead pattern

Competências Técnicas

Frontend

// Error Boundary React
class ErrorBoundary extends Component {
  static getDerivedStateFromError(error) {
    return { hasError: true };
  }
  
  componentDidCatch(error, errorInfo) {
    logError(error, errorInfo);
  }
  
  render() {
    if (this.state.hasError) {
      return <ErrorFallback />;
    }
    return this.props.children;
  }
}

Backend

// Custom Error Class
class AppError extends Error {
  constructor(message, statusCode, isOperational = true) {
    super(message);
    this.statusCode = statusCode;
    this.isOperational = isOperational;
    Error.captureStackTrace(this, this.constructor);
  }
}

// Async handler wrapper
const asyncHandler = (fn) => (req, res, next) => 
  Promise.resolve(fn(req, res, next)).catch(next);

Retry com Backoff

async function retryWithBackoff(fn, maxRetries = 3) {
  for (let i = 0; i < maxRetries; i++) {
    try {
      return await fn();
    } catch (error) {
      if (i === maxRetries - 1) throw error;
      await sleep(Math.pow(2, i) * 1000);
    }
  }
}

Circuit Breaker

const circuitBreaker = new CircuitBreaker(serviceCall, {
  timeout: 3000,
  errorThresholdPercentage: 50,
  resetTimeout: 30000
});

Padrões de Logging

Estrutura JSON

{
  "timestamp": "2024-01-15T10:30:00Z",
  "level": "ERROR",
  "message": "Failed to process payment",
  "correlationId": "req-123-abc",
  "userId": "user-456",
  "endpoint": "POST /api/payments",
  "error": {
    "name": "PaymentDeclined",
    "message": "Card declined by issuer",
    "code": "PAYMENT_001"
  },
  "stack": "...",
  "context": {
    "amount": 99.90,
    "currency": "BRL"
  }
}

Monitoring

Ferramentas

• Sentry (error tracking)
• Datadog
• New Relic
• CloudWatch Logs

Alertas

• Error rate threshold
• Response time degradation
• Uncaught exceptions
• Promise rejections

Boas Práticas

1. Never throw raw errors - Always wrap in custom error classes
2. Log context, not just errors - Include request ID, user ID, params
3. Fail gracefully - Show user-friendly messages
4. Circuit breaker for external services - Prevent cascade failures
5. Retry with exponential backoff - Don't hammer failing services
6. Global error handlers - Catch unhandled rejections
7. Error monitoring - Know about errors before users report
8. Document error codes - Team-wide understanding