Ingestion controls govern and report tenant trace volume. They are separate from sampling and retention.

Tenant usage limits

OpsRamp exposes trace-ingestion limits for daily and monthly reporting periods, with values expressed in millions of spans. Usage above configured thresholds can trigger warning or critical notifications; the configured limit is not a hard rejection threshold for trace traffic.

Treat limits and thresholds as client- and release-specific. Confirm the active setting, notification recipients, and escalation process with the client administrator.

Control actual volume

Use SDK sampling, trace-proxy sampling, or a configured collection pipeline to reduce the trace data forwarded for storage. Do not rely on an ingestion notification to throttle an application. Review span count per request and custom attribute cardinality alongside total volume.

Access

Trace Monitoring must be enabled for the client. Viewing trace usage requires TRACE_VIEW, and changing ingestion limits requires TRACE_MANAGE. Assign permissions through the client’s role-management process.