Rate Limiting and 429 Errors

What to do when you hit rate limits.

What Causes 429 Errors

The Lognitor API returns HTTP 429 (Too Many Requests) when:

1. Monthly log quota exceeded — you've sent more logs than your plan allows
2. Request rate limit — too many API requests per second

Handling in SDKs

All SDKs handle rate limiting automatically:

• Retry with exponential backoff
• Respect the Retry-After header
• Buffer logs during the backoff period

You don't need to handle 429s in your application code.

Reducing Log Volume

If you're consistently hitting limits:

Lognitor.init({
  apiKey: 'your-key',
  minLevel: 'info',       // Drop debug logs
  batchSize: 50,          // Larger batches = fewer requests
  beforeSend: (log) => {
    // Drop noisy logs
    if (log.message.includes('healthcheck')) return null;
    return log;
  },
});

Monitoring Usage

Check your log count in the dashboard header. Set up a usage alert to get notified at 80% and 95% thresholds.

Upgrading

If your application genuinely needs more logs, upgrade your plan for higher quotas.