For the complete documentation index, see llms.txt. Markdown versions are available by appending .md to documentation URLs.

Cost Control and Optimization in SigNoz

SigNoz Cloud - This page applies to SigNoz Cloud editions.
Self-Host - This page applies to self-hosted SigNoz editions.

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.

Analyze Ingestion Volume

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:

Phase 3: Validation

After deploying a change, verify the result.

  1. 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.
  2. 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):

Ingestion 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.

Is this page helpful

Last updatedAugust 14, 2026

Edit on GitHub