Intelligent Core tracing

src/content/docs/distributed-tracing/concepts/introduction-distributed-tracing.mdx

@@ -41,6 +41,24 @@ Distributed tracing collects data as requests travel from one service to another
   Here is an example of a web transaction where agents measure the time spent in each service. Agents then send that timing information to New Relic as spans, and the spans are combined into one distributed trace.
 </figcaption>
 
+## Control your distributed tracing data ingestion with APM agent configuration [#span-configuration]
+
+As you scale distributed tracing, you might want more control over data volume. Partial granularity distributed traces provide controlled ingestion, allowing you to capture data that really matters while managing data volumes effectively. APM agents provide configurable controls to ingest data in a controlled manner while maintaining the visibility you need.
+
+APM agent configuration helps you:
+
+* **Control ingestion** by configuring span volume and attributes
+* **Fill instrumentation gaps** with lightweight traces from all services
+* **Accelerate adoption** with controlled ingestion entry points for new services
+
+You get three configuration options for partial granularity distributed traces:
+
+* **Option 1 (Span filtering):** Reduce span count by 50-80% by removing in-process spans
+* **Option 2 (Span filtering + attribute reduction):** Reduce data volume by 60-75% by removing in-process spans and limiting attributes
+* **Option 3 (Maximum reduction):** Reduce data volume by 70-85% with span filtering, attribute reduction, and duplicate compression
+
+These options work at the service level—you can use full distributed tracing for business-critical services while using span configuration for supporting services. For more information, see [Control distributed tracing data volume](/docs/distributed-tracing/core-tracing/introduction-core-tracing).
+
 ## Get started[#learn-more]
 
 See these distributed tracing topics: