|
4 | 4 | <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
5 | 5 | <meta charset="utf-8">
|
6 | 6 | <link rel="stylesheet" href="toc.css">
|
| 7 | +<link rel="stylesheet" href="bootstrap/css/bootstrap.min.css"> |
7 | 8 | </head>
|
8 | 9 | <body>
|
9 |
| -<ul class="toc"></ul> |
| 10 | +<ul class="toc"><li> |
| 11 | +<a href="#opentelemetry">OpenTelemetry</a><ul><li> |
| 12 | +<a href="#configuring-opentelemetry">Configuring OpenTelemetry</a><ul> |
| 13 | +<li> |
| 14 | +<a href="#limitations">Limitations</a><ul></ul> |
| 15 | +</li> |
| 16 | +<li> |
| 17 | +<a href="#exporting-opentelemetry-only-traces">Exporting OpenTelemetry-only traces</a><ul></ul> |
| 18 | +</li> |
| 19 | +</ul> |
| 20 | +</li></ul> |
| 21 | +</li></ul> |
| 22 | +<h1 id="opentelemetry">OpenTelemetry</h1> |
10 | 23 | <p><strong>ATTENTION</strong>:</p>
|
11 | 24 | <p><strong><em>OpenTelemetry support is currently “experimental”. It may be subject to breaking changes between minor versions, and is not yet recommended for use in production or other sensitive environments.</em></strong></p>
|
12 | 25 | <p>If you are interested in using this feature experimentally, please contact the dd-trace-rb maintainers; we would be happy to provide you with more information!</p>
|
|
35 | 48 | </tr>
|
36 | 49 | </tbody>
|
37 | 50 | </table>
|
38 |
| -<h4 id="configuring-opentelemetry">Configuring OpenTelemetry</h4> |
| 51 | +<h2 id="configuring-opentelemetry">Configuring OpenTelemetry</h2> |
39 | 52 | <ol type="1">
|
40 | 53 | <li>
|
41 | 54 | <p>Add the <code>ddtrace</code> gem to your Gemfile:</p>
|
@@ -68,7 +81,7 @@ <h4 id="configuring-opentelemetry">Configuring OpenTelemetry</h4>
|
68 | 81 | <p><a href="#integration-instrumentation">Integration instrumentations</a> and OpenTelemetry <a href="https://opentelemetry.io/docs/instrumentation/ruby/automatic/">Automatic instrumentations</a> are also supported.</p>
|
69 | 82 | </li>
|
70 | 83 | </ol>
|
71 |
| -<h5 id="limitations">Limitations</h5> |
| 84 | +<h3 id="limitations">Limitations</h3> |
72 | 85 | <p>There are a few limitations to OpenTelemetry Tracing when the APM integration is activated:</p>
|
73 | 86 | <table style="width:100%;">
|
74 | 87 | <colgroup>
|
@@ -127,7 +140,7 @@ <h5 id="limitations">Limitations</h5>
|
127 | 140 | </tr>
|
128 | 141 | </tbody>
|
129 | 142 | </table>
|
130 |
| -<h5 id="exporting-opentelemetry-only-traces">Exporting OpenTelemetry-only traces</h5> |
| 143 | +<h3 id="exporting-opentelemetry-only-traces">Exporting OpenTelemetry-only traces</h3> |
131 | 144 | <p>You can send OpenTelemetry traces directly to the Datadog agent (without <code>ddtrace</code>) by using <a href="https://open-telemetry.github.io/opentelemetry-ruby/opentelemetry-exporter-otlp/latest">OTLP</a>. Check out our documentation on <a href="https://docs.datadoghq.com/tracing/setup_overview/open_standards/#otlp-ingest-in-datadog-agent">OTLP ingest in the Datadog Agent</a> for details.</p>
|
132 | 145 | <p>Datadog APM spans will not be sent through the OTLP exporter.</p>
|
133 | 146 | </body>
|
|
0 commit comments