Merge pull request #23083 from newrelic/docs/opentelemetry-api-support-agents

opentelemetry api support agents

Author: PallaviWrite

.gitignore

@@ -94,3 +94,8 @@ src/images/infrastructure_screenshot_full_sonarqube-dashboard.webp
 
 # Claude Code documentation (local only)
 .claude/
+
+# Documentation reference files (local only)
+EMAIL_TEMPLATE_AGENT_TEAMS.md
+OTEL_DOCS_STATUS.md
+SME_QUESTIONS_OTEL_API_SUPPORT.md

src/content/docs/apm/agents/go-agent/configuration/distributed-tracing-go-agent.mdx

@@ -15,11 +15,11 @@ redirects:
 freshnessValidatedDate: never
 ---
 
-Distributed tracing allows you to see the entire journey of your requests throughout a [distributed system](/docs/distributed-tracing/concepts/introduction-distributed-tracing). For the Go agent, we offer two types of distributed tracing (for more details, see [How span sampling works](/docs/understand-dependencies/distributed-tracing/get-started/how-new-relic-distributed-tracing-works#sampling)):
+Distributed tracing allows you to see the entire journey of your requests throughout a [distributed system](/docs/distributed-tracing/concepts/introduction-distributed-tracing). For the Go agent, we offer two types of distributed tracing (for more details, see [How span sampling works](/docs/distributed-tracing/concepts/how-new-relic-distributed-tracing-works/#sampling)):
 
-* Standard (head-based sampling): Before any traces arrive, we determine a set percentage of traces to accept and analyze. This gives you a solid starting point to see how tracing can help you. It is turned on by default in Go agents 3.16.0 and higher.
+* Standard (head-based sampling): Before any traces arrive, we determine a set percentage of traces to accept and analyze. This gives you a solid starting point to see how tracing can help you. It is turned on by default in Go agents 3.16.0 and higher. By default, the Go agent samples 10 traces per minute, with a max span limit of 2000 spans per minute.
 
-* Infinite Tracing (tail-based sampling): Our cloud-based service accepts all your traces and then sorts through them to find the most important. Infinite tracing analyzes all of your traces and gives you configuration options to sample the traces that matter most to you.
+* Infinite Tracing (tail-based sampling): Our cloud-based service accepts all your traces and then sorts through them to find the most important. Infinite Tracing analyzes all of your traces and gives you configuration options to sample the traces that matter most to you.
 
 Whether you just want to try out standard distributed tracing (head-based sampling) or also want to set up Infinite Tracing (tail-based sampling), you need to start by setting up standard tracing.
 
@@ -111,9 +111,7 @@ This is the best approach to set up [standard distributed tracing](/docs/distrib
 
 ## Infinite Tracing (optional) [#infinite-tracing]
 
-[Standard distributed tracing](#quick-start-apm) for APM agents [captures up to 10 traces per minute](/docs/distributed-tracing/concepts/how-new-relic-distributed-tracing-works/#trace-origin-sampling), but if you want us to analyze all your data and find the most relevant traces, you can set up [Infinite Tracing](/docs/understand-dependencies/distributed-tracing/infinite-tracing/introduction-infinite-tracing).
-
-Before you start, first ensure you meet [the requirements](/docs/understand-dependencies/distributed-tracing/infinite-tracing/introduction-infinite-tracing#requirements).
+With Infinite Tracing (tail-based sampling) we can analyze all of your data and determine which traces are the most relevant.
 
 <Steps>
   <Step>

src/content/docs/apm/agents/java-agent/configuration/distributed-tracing-java-agent.mdx

@@ -10,9 +10,9 @@ freshnessValidatedDate: never
 
 Distributed tracing allows you to see the entire journey of your requests throughout a [distributed system](/docs/distributed-tracing/concepts/introduction-distributed-tracing). For the Java agent, we offer two types of distributed tracing (for more details, see [How span sampling works](/docs/understand-dependencies/distributed-tracing/get-started/how-new-relic-distributed-tracing-works#sampling)):
 
-* Standard (head-based sampling): Before any traces arrive, we determine a set percentage of traces to accept and analyze. This gives you a solid starting point to see how tracing can help you. It is turned on by default in Java agents 7.4.0 and higher.
+* Standard (head-based sampling): Before any traces arrive, we determine a set percentage of traces to accept and analyze. This gives you a solid starting point to see how tracing can help you. It is turned on by default in Java agents 7.4.0 and higher. By default, the Java agent samples 120 traces per minute, with a max span limit of 2000 spans per minute.
 
-* Infinite Tracing (tail-based sampling): Our cloud-based service accepts all your traces and then sorts through them to find the most important. Infinite tracing analyzes all of your traces and gives you configuration options to sample the traces that matter most to you.
+* Infinite Tracing (tail-based sampling): Our cloud-based service accepts all your traces and then sorts through them to find the most important. Infinite Tracing analyzes all of your traces and gives you configuration options to sample the traces that matter most to you.
 
 Whether you just want to try out standard distributed tracing (head-based sampling) or also want to set up Infinite Tracing (tail-based sampling), you need to start by setting up standard tracing.
 
@@ -99,11 +99,9 @@ This is the best approach to set up [standard distributed tracing](/docs/distrib
   </Step>
 </Steps>
 
-## Infinite Tracing [#infinite-tracing]
+## Infinite Tracing (optional) [#infinite-tracing]
 
-[Standard distributed tracing](#quick-start-apm) for APM agents [captures up to 10 traces per minute](/docs/distributed-tracing/concepts/how-new-relic-distributed-tracing-works/#trace-origin-sampling), but if you want us to analyze all your data and find the most relevant traces, you can set up [Infinite Tracing](/docs/understand-dependencies/distributed-tracing/infinite-tracing/introduction-infinite-tracing).
-
-Before you start, first ensure you meet [the requirements](/docs/understand-dependencies/distributed-tracing/infinite-tracing/introduction-infinite-tracing#requirements).
+With Infinite Tracing (tail-based sampling) we can analyze all of your data and determine which traces are the most relevant.
 
 <Steps>
   <Step>