Data ingestion rate limit exceeded: New Relic agent configuration

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:

1. When an application moves from the free tier to a paid tier, does New Relic One automatically raise the ingestion rate limit, or does the user need to adjust trace_sampling or transaction_tracer.enabled manually?
2. If the platform does not auto‑adjust, what is the exact threshold or rule that determines the new rate limit?
3. What is the impact on billing if transaction tracing remains enabled but sampling is reduced to 1 % on a low‑traffic workload?