Ingestion Limits let you place hard caps on telemetry data ingested per ingestion key, independent of what the applications are sending. This is a SigNoz Cloud-only feature.
The primary use case is non-production environment governance: prevent a misconfigured dev or staging service from generating an unexpectedly large bill by capping ingestion before it reaches your paid quota.
How to Set a Limit
Limits are configured per-signal on an ingestion key. The full step-by-step procedure is in the ingestion keys documentation:
Add Limits to an Ingestion Key
In summary:
- Navigate to Settings > Ingestion Settings in SigNoz Cloud.
- Click the target ingestion key to open its dropdown.
- Select the signal to limit (Logs, Traces, or Metrics).
- Click + Limits, enter a limit value, and click Save.
Limits reset daily. Once the limit is hit within the day, SigNoz drops further data for that signal until midnight UTC.
Next Steps
- Return to Cost Control Overview for the full optimization flow.
- Set up Cost Meter Alerts to be notified when ingestion volume is approaching your limit.
- See Ingestion Keys for full key management, including modifying and removing limits.
Get Help
If you need help with the steps in this topic, please reach out to us on SigNoz Community Slack. If you are a SigNoz Cloud user, please use in product chat support located at the bottom right corner of your SigNoz instance or contact us at cloud-support@signoz.io.
