Overview
Telemetry data has a cost. In SigNoz Cloud, ingestion volume determines your costs.
In both cases, a large fraction of ingested volume comes from a small number of high-volume sources: high-cardinality metrics, health check routes generating millions of spans, or verbose debug logs.
This guide walks you through identifying and reducing that volume across three phases: Analysis, Execution, and Validation.
Optimization Flow
Phase 1: Analysis
Identify which signal, service, and environment is driving your ingestion volume. Use the right SigNoz feature for the time window you are investigating.
Phase 2: Execution
Once you have identified the high-volume source, apply the appropriate fix.
Proceed to the guide for the signal you want to reduce:
- Optimize Metrics: Drop unused metrics or aggregate high-cardinality labels.
- Optimize Traces: Reduce trace volume through head-based or tail-based sampling.
- Optimize Logs: Filter verbose logs at the Collector.
Phase 3: Validation
After deploying a change, verify the result.
- The Cost Meter Dashboard uses
signoz.meter.*metrics which aggregate hourly. For immediate feedback, use the relevant Explorer (Logs, Traces, or Metrics Explorer) to confirm the change is taking effect. - Configure Cost Meter Alerts to be notified when ingestion volume crosses your expected threshold.
Non-Production Enforcements
To apply hard ingestion caps on Dev or Staging environments regardless of telemetry content (SigNoz Cloud only):
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.