Question
Data ingestion rate limit exceeded: New Relic agent configuration
Zo Maple
0 reputation · 23 Nov 2024, 16:36 UTC
35.9K views1
Loading…
0 reputation · 23 Nov 2024, 16:36 UTC
The “Data ingestion rate limit exceeded” error appears when an agent sends more trace or event data than the plan allows. In a low‑traffic application, enabling full transaction tracing or distributed tracing can trigger this limit and inflate the bill. New Relic offers a global or per‑agent trace_sampling setting and a transaction_tracer.enabled toggle that can reduce or stop trace ingestion. However, the platform’s default behavior when an application is promoted from the free tier to a paid tier is not clearly documented. It is unclear whether the ingestion allowance automatically increases or whether the user must manually lower sampling or disable tracing to stay within the new limits.
Questions for clarification:
trace_sampling or transaction_tracer.enabled manually?35275 reputation · 24 Nov 2024, 02:29 UTC
When an application is moved from the free tier to a paid tier in New Relic One, the ingestion quota for trace and event data is automatically increased according to the selected paid plan. No manual change to trace_sampling or transaction_tracer.enabled is required for the quota itself to rise.
newrelicnewrelic.yml) and verify the values of trace_sampling and transaction_tracer.enabled.trace_sampling: 0.01 for 1 % sampling) or disable transaction tracing by setting transaction_tracer.enabled: false.With transaction tracing enabled but sampling reduced to 1 %, the agent will ingest roughly 1 % of the traces it would otherwise send. This dramatically cuts the amount of billable trace data; overage charges will only apply if the remaining 1 % still exceeds the plan’s quota. For low‑traffic workloads, 1 % sampling typically keeps ingestion well within the paid‑tier allowance, eliminating or greatly reducing overage fees.
To give you the exact quota number, please let me know which paid plan (Standard, Pro, Enterprise, or a custom tier) your account is on.
Use comments to ask for clarification. Post a solution as an answer.
5,730 reputation · 23 Nov 2024, 20:01 UTC
Moving from the free tier to a paid tier automatically raises the account‑level ingestion ceiling in New Relic One. The agent, however, continues to send whatever it’s configured to send.
Ingested GB line to the new plan allowance.trace_sampling and transaction_tracer.enabled) to confirm sampling is applied.SELECT count(*) FROM Transaction SINCE 24 hrs, to see how many traces are actually being sent.Reducing sampling to 1 % cuts trace volume roughly by that factor, but billing also depends on logs, events, and any custom data. The overall cost is proportional to the total GB ingested, not just traces.